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. 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]." The first problem can be solved by using the "su -" command. Note that
OK. I understand what you're saying here, but I'm from a Windows
environment and not really used to Linux permissions. Basically, I have
three users who are administrators on this server (all my servers
actually). The whole purpose of authentication against the Active
Directory is so that I can provide single sign-on capability to these
users and just give root a complex password that I don't have to give
out to everyone. If they have to su to do anything on the box, then
there's really no point in using AD authentication. Is this the case,
or is there some way I can assign certain permissions to these users?
-----Original Message-----
From: Jerry Feldman [mailto:gaf@blu.org]
Sent: Monday, March 13, 2006 8:12 AM
To: suse-linux-e@suse.com
Subject: Re: [SLE] Stupid newbie user rights question
On Monday 13 March 2006 8:54 am, Drew Burchett wrote:
the
hyphen allows him/her to become root and makes the terminal perform as a
login shell. This will cause him/her to get root's PATH.
Note that he needs to use either the "su" command or "sudo" or "sux" to
become root. Just because he is in root's group does not extend roots
ownership privileges to him. And, you never want to regular user to have
admin permissions per se. The convention is that everyone, including
admins
run as normal users and become root (or log in as root) when they need
to.
I think your second issue is probably related to this, and an "su -"
should
solve both.
--
Jerry Feldman