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

exim configuration



I was wondering someting about how exim is configured.
This stems from my attempts to get noflushd working on my notebook.

The first thing that I've noticed is that noflushd keeps getting interrupted by a cron job that keeps dumping 'exim -q' into the process list and hence restarting the hard drives.

The second thing I noticed is that inetd.conf holds an entry for exim to answer the SMTP port queries.

Given that this is true, there really isn't any need for the exim entry in /etc/init.d/ and the subsequent entries in /etc/rc#.d/. I removed them all using update-rc.d and found that exim still delivers and receives email just fine. This might be considered a configuration option somewhere. This is a bug that I have since reported since there is both a daemon and a inetd.conf listing.

From the README.Debian file there is mention that I might change the /etc/cron.d/exim script. What would I change it to so that the application, exim, does not keep trying to run when I'm trying to save battery life?

I understand that it might be necessary to have a periodic command for 'exim -q' for everything that couldn't get delivered right away from the inetd instance of exim. But every 15 minutes seems a bit much if you consider that often times power savings are often in junction with no internet connection and therefore a longer delay would be reasonable.

In any event, how would you modify the content of /etc/cron.d/exim as implied by this README.Debian file? From all I can gather, changing the run times would benefit. Other than that, I don't see much point in having it around at all. A simply daily anacron entry could clear out the queue, or changing this to 0 */4 * * * would suffice to. Right or Wrong? Anything I'm missing here?



Reply to: