On Tue, 2007-03-06 at 16:34 +0100, Marc Haber wrote: > On Tue, 06 Mar 2007 09:47:27 -0500, Arthur Hagen > <[EMAIL PROTECTED]> wrote: > >This reminds me of one machine I inherited where an hourly status report > >always came in 15 minutes late. Checking, I found that the status > >report was run at the top of the hour, and a /usr/lib/sendmail -qf cron > >job was run at 0,15,30,45 past the hour. Changing the queue flush cron > >to 1,16,31,46 fixed that problem. :-) > > With exim, it is a good idea not to start queue runners from cron.
Why, exactly? Please be technical. For a machine that doesn't need an smtp listener, it frees up having an unnecessary daemon running except at queue run time. That is, to my knowledge, the preferred way of running both exim and sendmail on a system without an SMTP listener. (For a machine that has to accept smtp, it's of course somewhat different, but that's not what was discussed here. And even then, for an extremely busy mailing list, I've spawned additional queue runners from cron for part of the day to reduce the minimum time to delivery (MTTD) at the cost of network traffic, while falling back to only the exim queue interval at other times of the day, to maximise throughput and reduce network traffic at the expense of MTTD.) Regards, -- *Art -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/
