On 13/03/06 07:54, Drew Burchett wrote:
I'm assuming that this is a user rights problem, although with my limited knowledge it may very well be something else. I've got a Suse 10 box that authenticates against my Active Directory. Everything works great and my users can log on. However, there is one account that I wish to have administrative privileges on the machine. To that end, I have placed that user in the root group. He is able to log in and work with the box, but I've noticed two problems:
1. The PATH variable isn't set to the same as it is for root. I'm not using any sort of bashrc script for root except what is in bashrc.local, so I assumed that it would be the same. This isn't a big deal because I can create a bashrc script for that user if I need.
There are more files than these. I think these are all the files that contribute to a user profile: /etc/login.defs -- provides the basic profile which may be modified later. There are separate PATHs here for root and for an ordinary user. /etc/profile and /etc/profile.local /etc/bash.bashrc and /etc/bash.bashrc.local Every ordinary user also has a ~/.bashrc and ~/.profile It's been suggested elsewhere that you should look at using the su and sux commands, which require the root password but leave the user in a root login shell. A couple have also suggested sudo, which can be configured so a password is not required. It does, however, not run in a root environment. Given what you wish to do, perhaps the only solution available to you is to allow that one user to have the root password. If you trust him with root priviledges, surely you trust him with that password.
2. When running Yast, the installation source is the same (an FTP site that I use), but when I go to install something while running as this user, Yast tells me "Cannot access installation media SUSE LINUX Version 10.0 CD 1." Show details tells me "ERROR (Media:unable to write file) [/media.1/media]."
You certainly do not wish to be running Yast as an ordinary user, even if that user is in group root. There are places where even group root has no permissions, but which must be accessed during various system processes. I would think system configuration would be the one place where running as the root user is absolutely essential.