Sorry for the thread necromancy here…
The su command does not replace the environment of the user unless you give it the “-” option, like so:
[code]
su – odadmin
[/code]
This behavior is consistent on any UNIX platform whether you are using LDAP, NIS, or plain old /etc/passwd. As one of the previous posters pointed out, it looks like you are getting your group membership information just fine, but the directory /root is not group or world readable (which is a good thing).
You should be able to as root type “ls -ld /root” and see the directory permissions. Then after you have run the su command, type “groups” and you should see all of the groups that your odadmin user is a member of. Chances are that it’s either not a member of the group root or that the permissions for /root are “drwx——“.
[QUOTE][u]Quote by: bowmasters[/u][p]Well what ends up happening is I still get the message “/root/.bashrc: Permission denied”
It looks like it isn’t actually loading the proper profile information for the user. If I issue the command “cd ~” it tries to cd to /root:
[code]bash-3.2$ cd ~
bash: cd: /root: Permission denied
[/code]
Other machines bound to this LDAP server don’t have this problem. They correctly cd to the home directory Specified in the LDAP profile.
Also, when I try to su to the directory user from a non-root privileged shell it asks for a password, but simply tells me “Sorry” regardless Of whether I entered it right or not[/p][/QUOTE]
Recent Comments