topic Re: User group incorrect in Operating System - HP-UX

User group incorrect

Krishnan Viswanathan — Tue, 15 Jan 2002 23:23:12 GMT

I am finding inconsistencies when I execute the id command as a normal user and as a super user. For example,

$ id smshpd
uid=15900(smshpd) gid=3026(sms) groups=201(staff)

# id smshpd
uid=15900(smshpd) gid=3026(sms)

I am seeing this difference for almost all users. Additional groups/incorrect secondary groups are shown when I run the "id" command as a normal user.

Is this how hpux is supposed to work? or is this a bug ? (I tried this on 3 systems and had the same problem)

Thanks

Re: User group incorrect

Wilfred Chau_1 — Tue, 15 Jan 2002 23:31:37 GMT

They should be the same. check your /etc/group file. run id -G smshpd, what do you see?

Re: User group incorrect

Krishnan Viswanathan — Tue, 15 Jan 2002 23:35:16 GMT

id -G returns the gid of groups when a normal user executes it (i mean it is incorrect)
See my original message for comparision

$ id -G smshpd
3026 201

thanks

Re: User group incorrect

Patrick Wallek — Tue, 15 Jan 2002 23:43:21 GMT

Do you have /etc/logingroup linked to /etc/group?

If not do so and then see what happens.

Re: User group incorrect

Wilfred Chau_1 — Wed, 16 Jan 2002 00:03:17 GMT

$ id smshpd
uid=15900(smshpd) gid=3026(sms) groups=201(staff

you must have 15900:3026 in /etc/passwd for this user. But this user is put in the staff group in /etc/group.

Re: User group incorrect

Krishnan Viswanathan — Wed, 16 Jan 2002 00:05:39 GMT

Well, the problem is not restricted just to one user, it is across many systems and many users.. (may be a patch will solve it ?)

Re: User group incorrect

Mark Fenton — Wed, 16 Jan 2002 01:02:18 GMT

If the output differs only based on the user, I would suspect that either the path of root points to a different executable, or the root profile contains an alias that specifies options.

To check:

#which id
/usr/bin/id

#env ((to check search path, etc.))

hth

Re: User group incorrect

Darrell Allen — Wed, 16 Jan 2002 02:45:37 GMT

Hi,

I thought I saw what was happening. I just tested it on an 11.0 systsm and found...

When a non-superuser executes "id loginid" the output lists the uid, primary group, and then only the secondary groups that loginid AND the user executing the command are both in. When I ran the same "id loginid" command as root, all secondary groups for loginid were listed.

I tested the above as and for a couple of users and the results each time were what I list above.

Then I looked at your question again and assuming your first output is by a non-superuser and the second is by root, it's reversed from what I saw!

Go figure!

Darrell