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.
And consequently almost everything on the machine got owned by root, save for a few /dev's that wouldn't let me. I've got a decent amount of it back in working order but now only root can use the su command with any effectiveness. Any other account that tries to use su hesitates before receiving an error that the password is incorrect. The password is correct so I'm led to believe I've made some vital file in the authentication process inaccessible to anyone but root. I'm guessing it's one that should be owned by a system user rather than root, or maybe I need to re-SETUID root on one or all of the files involved. The problem is, I don't know all of the files involved... /usr/bin/su, /etc/passwd, /etc/shadow. Can anyone help? This is on a FC3 distribution with everything installed (if not all used).
Also, since this little accident my System Log has been getting spammed with...
Thanks Mara, that cleared the spam up. The GID was set to 'adm'. I left it alone after Googling the phrase and finding one guy's comment that it was supposed to be that way. So much for that.
Oh, I found another quirk. The locate command is spitting back access-denied problems about the /var/run/slocate.db file to the regular users. The UID is set to 'root' currently, and the GID is 'slocate'. Apparently there is no 'slocate' user, only a group. What user is the slocate.db supposed to be? Maybe this is a case for chmod 4640? (Well that didn't work)
Hmm... deleting the old database and updatedb'ing anew didn't fix it either. Must be inheriting some bad permissions?