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.
There are things like Log Rotators that assist in log removal/archiving. You could use those, then periodically run a cron to clean out the old logs if you didn't wanna keep them around.
And mail servers save logs in various locations, my Postfix system on Gentoo saves them:
But I'm running metalog, so you might wanna check with your system logger to see where it stores it's logs. Most likely it's going to be a subdirectory of /var/log though
Log files are created if they do not exist. It's normal. You can setup a cron job to remove these files on a weekly/daily/hourly basis if you'd like.
As for the sending/receiving bit..
Were you able to send before you tapped out the partition? Did you manually remove any files when trying to free up space? What files were removed when you removed X? If you've still got your mail server files on your box, nothing should have changed? You might need to restart the server though, follow the documentation for it to restart it.
I haven't tried to partition the HD.. Yes.. we have removed a file manually (/var ... but we have copy it back, thinking it has no effect on the HD space). I think its the main reason why our server cant send mails.. I restarted postfix here is the error message
postfix/postfix-script: warning : not owned by postfix: /var/spool/postfix/incoming/E/4
postfix/postfix-script: warning : not owned by postfix: /var/spool/postfix/public
postfix/postfix-script: warning : not owned by postfix: /var/spool/postfix/saved
postfix/postfix-script: warning : not owned by group postdrop: /var/spool/postfix/public
postsuper: fatal: scan_dir_push: open directory defer: Permission Denied
postfix/postfix-script: fatal: Postfix integrity check failed!
What should we do then??
Last edited by ann_tulip18; 07-09-2003 at 09:26 PM.
Hmm... Let's try to setup the ownership then:
chown -R postfix.postdrop /var/spool/postfix (this needs to be run by root)
Now try restarting postfix again.
**I've looked up my own permissions, try this instead:
chown root.root /var/spool/postfix
chown postfix.root /var/spool/postfix/*
chown postfix.maildrop /var/spool/postfix/maildrop /var/spool/postfix/public
I tried it... and then restart the postfix (postfix start) theres a message again:
postfix/postfix-script: warning : not owned by root: /var/spool/postfix/lib/libdb-3.3.so
postfix/postfix-script: warning : not owned by root : /var/spool/postfix/usr
postfix/postfix-script: warning : not owned by root : /var/spool/postfix/usr/lib
postsuper: Renamed to match inode nunmer: 230 messages
postsuper: warning: QUEUE FILE NAMES WERE CHANGED TO MATCH INODE NUMBERS
postfix/postfix-script: starting the Postfix mail system
Well, we can keep doing this if you'd like, eventually we should get all the permissions back. Another option is for you to use the upgrade option in the postfix source, this will go through and install and set correct permissions on all the new packages when installing postfix.
Well you could spend all this time, energy and heachache trying to fix your space issue by finding the space hog and figuring out how to uninstall it. Or you just ghost to a larger drive... ghost will resize the partitions to scale to the new drive automatically and you have the chance to adjust it at that point.
Or possibly a better fix for you might be to copy out all the mail spools, then google clarkconnect, download the 1.3 ISO, this is a redhat based distro that uses utilities like apt by default, is specifically designed to run as a mailserver/gateway and doesn't install a whole lot more than is needed to perform these functions. It also uses postfix by default rather than the historically bug ridden sendmail. You can perform the simpliest of administration on the local lan by point a browser at: https://mailserverip:81.
It has the advantage of being the only cookie cutter mail/web/ftp/gateway application distro I know of that doesn't overwrite manual changes or require you edit templates. It uses the same directory structure any redhat system uses.
It will take up to an hour to install if you've never done it before and have 50 users or so. You might lose the mail that is sitting on your server right now if you don't know how to move the mail spools back in place but that might not being to compare wit the mail you lose being down.