The file /etc/logrotate.d/exim does not restart exim after logs we rotated. This usually causes log messages continued to be written to an old file. Add the lines similar to ones used in /etc/logrotate.d/named postrotate /usr/bin/kill -HUP `cat /var/run/named.pid 2> /dev/null` 2> /dev/null || true endscript where pid file name should be /var/run/exim.pid
In addition. Do it in a way similar to httpd. One sighup to several files rotated. man logrotate , example here" /var/log/httpd/access.log /var/log/httpd/error.log { sharedscripts postrotate .... endscript } So postrotate script will be executed only once
That's a good idea. So you want something like this? (Please excuse bugzilla's annoying wrapping of the first line): /var/log/exim/exim_mainlog /var/log/exim/exim_rejectlog /var/log/exim/exim_paniclog { missingok postrotate /bin/kill -HUP `cat /var/run/exim.pid 2>/dev/null` 2> /dev/null || true endscript }
1. Yes, but just add sharedscripts keyword before postrotate so the signal will be delivired only once. Otherwise it will be delivered for every log file, so exim may be restarted three times. 2. It may make sence to change log files names to /var/log/exim/exim_main.log instead of /var/log/exim/exim_mainlog (.log extension), same thing with the other logs. In a similar as samba. Then logrotate script will be the following /var/log/exim/*.log { missingok noifempty sharedscripts postrotate /bin/kill -HUP `cat /var/run/exim.pid 2>/dev/null` 2> /dev/null || true endscript } This is exactly how it set in samba (the only problem with samba is samba pid files in wrong directory, I posted a bug report about this in http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=15343
Hmm. Path of least resistance ;) : /var/log/exim/exim_*log { missingok noifempty sharedscripts postrotate /bin/kill -HUP `cat /var/run/exim.pid 2>/dev/null` 2> /dev/null || true endscript } Look good to you? If so, then I'll commit the changes and build the package. Are there any other problems with exim that you've run into? Tim
This logrotate looks OK to me. >Are there any other problems with exim that you've run into? We did not test it very much yet, two weeks ago I decided to get rid of qmail (because of its license) and go with GPL-ed exim. It works ok, no problem so far. The only diference (compared to RedHat 7.0 beta) which I have is that I repackaged exim with exim-3.16 (latest stable). No problem so far.
OK. New package is exim-3.13-19. Tim
Just one thing: I think you mean "notifempty" in the logrotate script, rather than "noifempty". ("noifempty" may well work as a synonym - but I can't find it anywhere in the docs)
Nope. That's a screwup on my part :/ . Change it to notifempty when you install it.
Yes, it should be notifempty It was just misspelled in my posting. Also exim-3.16 was around for a while (since Aug 1) and seems being pretty stable. May be it worth to upgrade exim to 3.16?
Too late to do this now. The new maintainer of the exim package will probably do this for the release following 7.0, but that's his call. Tim