07-29-2009
Need to change permissions
Hi everyone,
There are couple of users of which i need to give 2 of the users admin rights so that they are able to run the administration commands like "zoneadm" and locale.
When logged in as root i am obviously able to do that.please suggest any way by which the other 2 user's permissions can be changed so that they too are able to run the above commands.
Last edited by DukeNuke2; 07-29-2009 at 11:29 AM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi ,
I have a situation where plenty of users log in to the same directory and put in files. When they put in the files, I need those files to become group writable (chmod g+w) automatically. I have no control over the users' profiles. Is there a way to do it? (1 Reply)
Discussion started by: praveen_indramo
1 Replies
2. UNIX for Advanced & Expert Users
Suppose, I want to execute unix commands. For that I have to go to ksh, but if I don't have execute permission to ksh itself then is there any way to change the permission of ksh? chmod command does not work for this because, I don't have permission to ksh itself... :)
Let me know, if you have... (3 Replies)
Discussion started by: ponnuvel
3 Replies
3. UNIX for Dummies Questions & Answers
Hi everyone,
There are couple of users of which i need to give 2 of the users admin rights so that they are able to run the administration commands like "zoneadm" and locale.
When logged in as root i am obviously able to do that.please suggest any way by which the other 2 user's permissions... (1 Reply)
Discussion started by: sankasu
1 Replies
4. UNIX for Dummies Questions & Answers
while trying to view the access permissions to file by "ls -lrt" command it is opening some files int the dir after that segmentation fault ie core is generarting the dir.will anybody please what is the problem. (1 Reply)
Discussion started by: rajkumar_g
1 Replies
5. OS X (Apple)
I purchased a 2TB hard drive, split it into two partitions, and formatted it as NTFS. I want to use the drive on my pc and my mac. How can I change the access permissions so Mac OS 10.4.11 will let me write to the drive?
I tried this:
$ chmod +a "admin allow write" /volumes/V2_Mac
chmod:... (3 Replies)
Discussion started by: Me&MyMac
3 Replies
6. Shell Programming and Scripting
Hi, I am creating a ksh script to search for a string of text inside files within a directory tree. Some of these file are going to be read/execute only. I know to use chmod to change the permissions of the file, but I want to preserve the original permissions after writing to the file. How can I... (3 Replies)
Discussion started by: right_coaster
3 Replies
7. UNIX for Dummies Questions & Answers
Is there any option with mv or cp command so that a file permissions and name of the file can be changed in single mv or cp command. I searched man mv but doesn't found any option like that. (3 Replies)
Discussion started by: Devesh5683
3 Replies
8. Shell Programming and Scripting
Hi
I have written the following script that later I want to put in cron,:
#!/bin/bash
_find="/usr/bin/find"
_paths="/moneta_polled01/mediation_gsm /moneta_polled01/mediation_mmsc"
for d in $_paths
do
$_find $d -type f -exec chmod 777 {} \;
done
but it does not seem to be... (8 Replies)
Discussion started by: fretagi
8 Replies
9. UNIX for Dummies Questions & Answers
Hi everyboy,
I've installed a Virtualbox on my computer, inside the VB i'm running RedHat.
So my problems it's that i need to run the scripts runasroot.sh to install the guest addiont, i'm doing this by console. I wrote chmod 775 ./runasroot.sh but doesn't works. I'm login as root user.
Any... (8 Replies)
Discussion started by: Newer
8 Replies
10. Solaris
Hi!
I have a dir in a server, that receives files with the wrong permissions, so I decide to put on a cron entry that changes its permitions, but because of the time gap, not all of them get changed.
What I did was the following:
... (14 Replies)
Discussion started by: fretagi
14 Replies
LEARN ABOUT LINUX
sudo_root
sudo_root(8) System Manager's Manual sudo_root(8)
NAME
sudo_root - How to run administrative commands
SYNOPSIS
sudo command
sudo -i
INTRODUCTION
By default, the password for the user "root" (the system administrator) is locked. This means you cannot login as root or use su. Instead,
the installer will set up sudo to allow the user that is created during install to run all administrative commands.
This means that in the terminal you can use sudo for commands that require root privileges. All programs in the menu will use a graphical
sudo to prompt for a password. When sudo asks for a password, it needs your password, this means that a root password is not needed.
To run a command which requires root privileges in a terminal, simply prepend sudo in front of it. To get an interactive root shell, use
sudo -i.
ALLOWING OTHER USERS TO RUN SUDO
By default, only the user who installed the system is permitted to run sudo. To add more administrators, i. e. users who can run sudo, you
have to add these users to the group 'admin' by doing one of the following steps:
* In a shell, do
sudo adduser username admin
* Use the graphical "Users & Groups" program in the "System settings" menu to add the new user to the admin group.
BENEFITS OF USING SUDO
The benefits of leaving root disabled by default include the following:
* Users do not have to remember an extra password, which they are likely to forget.
* The installer is able to ask fewer questions.
* It avoids the "I can do anything" interactive login by default - you will be prompted for a password before major changes can happen,
which should make you think about the consequences of what you are doing.
* Sudo adds a log entry of the command(s) run (in /var/log/auth.log).
* Every attacker trying to brute-force their way into your box will know it has an account named root and will try that first. What they do
not know is what the usernames of your other users are.
* Allows easy transfer for admin rights, in a short term or long term period, by adding and removing users from the admin group, while not
compromising the root account.
* sudo can be set up with a much more fine-grained security policy.
* On systems with more than one administrator using sudo avoids sharing a password amongst them.
DOWNSIDES OF USING SUDO
Although for desktops the benefits of using sudo are great, there are possible issues which need to be noted:
* Redirecting the output of commands run with sudo can be confusing at first. For instance consider
sudo ls > /root/somefile
will not work since it is the shell that tries to write to that file. You can use
ls | sudo tee /root/somefile
to get the behaviour you want.
* In a lot of office environments the ONLY local user on a system is root. All other users are imported using NSS techniques such as
nss-ldap. To setup a workstation, or fix it, in the case of a network failure where nss-ldap is broken, root is required. This tends to
leave the system unusable. An extra local user, or an enabled root password is needed here.
GOING BACK TO A TRADITIONAL ROOT ACCOUNT
This is not recommended!
To enable the root account (i.e. set a password) use:
sudo passwd root
Afterwards, edit the sudo configuration with sudo visudo and comment out the line
%admin ALL=(ALL) ALL
to disable sudo access to members of the admin group.
SEE ALSO
sudo(8), https://wiki.ubuntu.com/RootSudo
February 8, 2006 sudo_root(8)