Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

What happens at 6:30 am (besides that fetchmail seems to crash)?



On Fri, Feb 23, 2007 at 08:04:05AM -0500, Laura Conrad wrote:
> It's more complicated than that.  It looks like if I have "set syslog"
> in /etc/fetchmailrc, the fetchmail log stuff is written to both
> mail.log and syslog.  syslog is rotated by cron.daily via sysklogd.
> Running the restart command syslogd runs (/etc/init.d/sysklogd
> reload-or-restart) doesn't seem to bother fetchmail.  I have not
> figured out what rotates mail.log.

Take a look at your /etc/syslog.conf -- I expect you will see
something like:
mail.* 		/var/log/mail.log

which tells syslog to store copies of all mail log messages in
that file. It also probably has something like:

*.*		/var/log/syslog

which puts copies of everything into that file.

So syslog is doing all the logging.

logrotate is probably responsible for the log rotation.

You might want to investigate getmail
http://pyropus.ca/software/getmail/

which, on the whole, is less buggy.

-dsr-

-- 
.. .----. --   .-. . .- -.. .. -. --.   -.-- --- ..- .-.   -- .- .. .-.. .-.-.-   .-- .... ---   . .-.. ... .   .. ... ..--.. 
http://tao.merseine.nu/~dsr/eula.html is hereby incorporated by reference.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org