Solaris 9 User/Group Account Misbehavior
There seems to be a special way of entering user and group accounts that makes the account and group assignments not work properly.
acmgr::300:root
anyone::400:acctmgr
anyone:x:500:400::/export/
acctmgr:x:200:300::/usr/lo
The symptoms are:
- acctmgr can not “cd / export/home/anyone” even though the permissions are 770.
- anyone can not login to the Gnome desktop from the console login screen
Cause
I just ran into this problem again and the only unusual thing that I remember is that I had made a mistake with the group number and used a number that was already assigned to another group. So I ran “pwconv” with two groups with the same number. I “vi” the passwd file and corrected the group number. Then the problem appeared (I think).
Resolution
I have tried deleting and reallocating the “/export/home/anyone” file. Reperformed a “chown anyone:anyone /export/home/anyone” and used userdel, grouped, useradd, groupadd, usermod to remake the accounts. This only worked sometimes!
I checked through the account definitions in passwd and group and they are correct. The error is persistent but I don’t know where the bad information is being kept…
Has anyone run into any thing like this?
Thanks, Allan
acmgr::300:root
anyone::400:acctmgr
anyone:x:500:400::/export/
acctmgr:x:200:300::/usr/lo
The symptoms are:
- acctmgr can not “cd / export/home/anyone” even though the permissions are 770.
- anyone can not login to the Gnome desktop from the console login screen
Cause
I just ran into this problem again and the only unusual thing that I remember is that I had made a mistake with the group number and used a number that was already assigned to another group. So I ran “pwconv” with two groups with the same number. I “vi” the passwd file and corrected the group number. Then the problem appeared (I think).
Resolution
I have tried deleting and reallocating the “/export/home/anyone” file. Reperformed a “chown anyone:anyone /export/home/anyone” and used userdel, grouped, useradd, groupadd, usermod to remake the accounts. This only worked sometimes!
I checked through the account definitions in passwd and group and they are correct. The error is persistent but I don’t know where the bad information is being kept…
Has anyone run into any thing like this?
Thanks, Allan
ASKER
Sorry, truss does not seem to work for "cd" - even as root all "cd" operations fail.
$ su
# truss cd /export/home/anyone
Fails with the same "Err #2 ENOENT" error.
$ su
# truss cd /export/home/anyone
Fails with the same "Err #2 ENOENT" error.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It turned out that the problem was with the .cshrc file. We use "umask 117" in .cshrc and I was doing a
cp -pR anyone1 anyone2
chown anyone2:anyone2 anyone2
and it did not change to ownership of .cshrc !!!
Thanks for your help, Allan who feels a bit foolish :-/
cp -pR anyone1 anyone2
chown anyone2:anyone2 anyone2
and it did not change to ownership of .cshrc !!!
Thanks for your help, Allan who feels a bit foolish :-/
You need to have your executable bit set on the directory for all users, i.e. permissions should be 775, not 770 for the /export/home/anyone directory.
BTW, Sun recommends using /usr/ucb/vipw to edit your password file - this keeps your password and shadow files consistent.
BTW, Sun recommends using /usr/ucb/vipw to edit your password file - this keeps your password and shadow files consistent.
ASKER
open ("var/ld/ld.conf", O_RDONLY) Err #2 ENOENT