Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
There is less than 24 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
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.
Based on the message you got I suspect someone did the old "chmod 777 *" trick trying to open up everything to the world because they didn't want to troubleshoot why whatever they were doing worked. Many things have security setups to prevent them from working if they are 777.
What the permissions on /etc/mail/trusted-users? On /etc/mail?
The message seems to imply you should NOT have write permission for "world" on it.
My /etc/mail and /etc/mail/trusted-users have:
drwxr-xr-x 3 root root 4096 May 11 08:55 /etc/mail
-rw-r--r-- 1 root root 127 Mar 14 2007 /etc/mail/trusted-users
The message seems to imply that you instead have something like:
drwxr-xrwx 3 root root 4096 May 11 08:55 /etc/mail
-rw-r--rw- 1 root root 127 Mar 14 2007 /etc/mail/trusted-users
The extra w in that position would be your problem. You can change to what I have by typing:
chmod 755 /etc/mail
chmod 644 /etc/mail/trusted-users.
However, if somebody did the chmod 777 * they may have started at root so you may have other issues as well. Verify your root (/) is not world writable:
ls -ld /
drwxr-xr-x 26 root root 4096 Sep 8 13:47 /
If it IS world writable you need to investigate everything from root down as:
1) It would leave you open to easy hacking.
2) As noted many things break when they are world writable to prevent this being done as a way for easy hacking.
Change permissions to 600, not 777. The error message complains about an insecure directory.
Thanks eager, However, when I changed the perms to 600, The sendmail service started but with errors:
/sbin/consoletype: error while loading shared libraries: libc.so.6: cannot open shared object file: Permission denied
Also, when trying to restart sendmail, the sm-client [Failed]
Also, my monitoring system (nagios) didn't open up due to the fact that it couldn't open the main config file, so I decided to test the permissions. I changed the perms to 711 which seemed to make everything happy. no errors when checking the nagios configs but sm-client still failed to start
Last edited by teknoratti; 10-24-2011 at 04:13 PM.