01-18-2013
Quote:
Originally Posted by
Scott
If you don't have root privileges, then you'd better ask someone who has
but the user is already into that group .. I just want one of change the default one.. still need the root access?
Thought it can be done without root access. Seems like need to raise ticket for the same to unix admin and have to wait for their SLA
10 More Discussions You Might Find Interesting
1. Solaris
I need to change group for a file elektro.log
currently the owner is buddy and group is assigned as other
i need to change the group to freinds
I issued this command
chgrp freinds elektro.log
but i encounetered error like "....not owner"
do i need to su as root to perform this action. (1 Reply)
Discussion started by: vilves
1 Replies
2. UNIX for Advanced & Expert Users
Hi...
-bash-3.00$ id -a
uid=1004(oracle) gid=101(oinstall) groups=101(oinstall),100(dba)
How to change gid from oinstall group to dba group?? (6 Replies)
Discussion started by: adzuanamir
6 Replies
3. Shell Programming and Scripting
I need to find all the files that have group Read or Write permission or files that have user write permission.
This is what I have so far:
find . -exec ls -l {} \; | awk '/-...rw..w./ {print $1 " " $3 " " $4 " " $9}'
It shows me all files where group read = true, group write = true... (5 Replies)
Discussion started by: shunter63
5 Replies
4. UNIX for Dummies Questions & Answers
Hello AIX gurus,
I have a requirement where I have to change user ID of user "myuser" from 100 to 200 and also the group ID of "mygroup" from 2 to 3. Please note that "myuser" has "mygroup" as it's primary group.
What steps do I need to follow for this and in what order? Also can you please... (2 Replies)
Discussion started by: sacguy08
2 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I am new for solaris...
how can we change default shell for any user and how to check that which shall currently we are in...... (1 Reply)
Discussion started by: lalit21984
1 Replies
6. UNIX for Advanced & Expert Users
Hi frnds,
I would like to change my default group.
I tried using newgrp, but it will change the group in that xterm only.
If i open a new xterm that setting is gone.
Also i tried by putting newgrp <my_grp> into the file .cshrc which will be run during startup. Eventhough its working, it is... (5 Replies)
Discussion started by: appualex
5 Replies
7. Ubuntu
Hi,
Anyone can help me on how to duplicate privileges and group for useroradb01 to userrootdb01. I have currently using "useroradb01" and create a newly user "userrootdb01".
I want both in the sames privileges and group. Please see the existing users list below;
drwxr-xr-x 53 useroradb01... (0 Replies)
Discussion started by: fspalero
0 Replies
8. Shell Programming and Scripting
I would like to replicate the functionality of chsh (or passwd -e) by awk.
This is what I got so far, but I think there should be an easier way to search and replace field $7 only for lines beginning with user_name:
awk -v user_name="$user_name" -v new_shell="$new_shell" -F: '$1 == user_name {... (2 Replies)
Discussion started by: nomad84
2 Replies
9. Linux
Hi,
I am working on setup a environment where only a specific user can upload the builds on htdocs of apache.
Now i want that a specific user can copy the builds on htdocs folder.
I created a group "deploy" and assign user1 and user2 to this group.
On Apache side i mentioned User=deploy... (3 Replies)
Discussion started by: sunnysthakur
3 Replies
10. Red Hat
Hi,
In the following output you can see the the user "richard" is a member on the team/group "developers":
# id richard
uid=10247(richard) gid=100361(developers) groups=100361(developers),10053(testers)
but in the following details of the said group (developers), the said user... (3 Replies)
Discussion started by: indiansoil
3 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)