Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Depending on how you do this, you could be opening your system up to attacks. For instance, malware could take advantage of elevated user accounts if they are logged in, or an incorrectly written script or command could wipe out the entire system.
I'm trying to think why you would want to do this on a systemwide level and can't think of a good one. Mind explaining what you are trying to accomplish?
Remove the user from the root group. You can use "su" and "sudo" to run commands as root. Your distro probably has a number of GUI system configuration wizards. If you run them from the menu, you will be prompted for the root password. After that, you will be running that program as root.
and delete the "# " at the front of the commented line for the "%wheel" group. You may also need to add yourself to the wheel group. Some distro's like Ubuntu add the first user to the %wheel group and have this group already configured to use sudo.
Please put your distro in your user profile. If you use Ubuntu, you already can use sudo, but we don't know this.
Actually you can extend user privileges by adding them to the root group, but even in this case those users will only be able to read/write/execute files that belong to group root and have their group permissions set to rwx. Files that belong to root, but have all group permissions disabled, can not be accessed by the root group.
Depending on what you want to achieve, this can even be handy. You only have to enable/disable group permissions on root owned file to fine-tune access to them
No. Please stop thinking about using the root group. Bad Idea. All of your programs and processes will inherit your group membership. You don't want to be running a browser with the root group ownership permissions. Besides, having to change the permissions of a file to allow root group permissions, you would still need to use su or sudo.
thanks to all for help and suggestion. two of us maintaining the system and we agreed to use 2 account to keep accountability and dont want to use su every time. we can do this in windows system so we thought this can be done in linux also. i tried sudo but there is one problem sudo can not execute all the command like deluser, etc. i am using cent os 5.2. can anyone suggest any other option to do it.
we can do this in windows system so we thought this can be done in linux also.
Which is one of, if not the reason(s) why Linux is more secure than Windows. I'm not familiar with the finer details of system security, but to the best of my knowledge you are going to have to use su or sudo and do a bit of researching into how to log the level of info you want to maintain the accountability you need.
If you trust each other enough, why not log in both as root
IMNSHO "trust" has nothing to do with it nor should it. If you want accountability then just configure auditing and ensure logging can't be tampered with: use kernel logging with like GRSecurity or Auditd, 'rootsh' to do userland logging of shell history, transmitting log lines to a remote syslog server and possibly parsing those there in real time could provide you with a good audit trail.
Yes, Users by standard use bin directories instead of sbin directories because of the different configuration of $PATH so try "sudo /usr/sbin/userdel <username>" and I bet it works . Reconfigure sudo as said above, reconfigure sudo...