I thought I sent the information.
The problem turned out to be a bug in logrotate triggered by the squid package.
I had had squid installed and removed it. When I removed it, squid's logrotate script failed, and the logrotate program stopped before it got around to rotating exim's logs.
So, the bug was reproducible, but it was not a bug in exim4. It is presumably best solved by making sure that logrotate doesn't terminate early on errors.
Andreas Metzler wrote:
On 2004-12-22 Andreas Metzler <[EMAIL PROTECTED]> wrote:
On 2004-12-22 Greg Kochanski <[EMAIL PROTECTED]> wrote:
Andreas Metzler wrote:
[...]
Logrotation works fine for me. Did you modify /etc/logrotate.d/exim4-base? What does logrotate -d /etc/logrotate.conf 2>&1 | grep -2 exim4 say?
logrotate -d /etc/logrotate.conf 2>&1 | grep -2 exim4
gives
reading config file cupsys
reading config info for /var/log/cups/*log
reading config file exim4-base
reading config info for /var/log/exim4/mainlog /var/log/exim4/rejectlog /var/log/exim4/paniclog
reading config file mysql-server
reading config info for /var/log/mysql.log /var/log/mysql/mysql.log /var/log/mysql.err /var/log/mysql/mysql.err
[...]
Hello, That looks bad, the part where logrotate actually considers the logfiles is missing, this should include stuff look like this:
rotating pattern: /var/log/exim4/mainlog /var/log/exim4/rejectlog /var/log/exim4/paniclog after 1 days (10 rotations) empty log files are not rotated, old logs are removed considering log /var/log/exim4/mainlog log does not need rotating
Could you send the complete un-grepped output of "logrotate -d /etc/logrotate.conf"?
Hello, Couild you please provide the information I asked for? Can you still reproduce the problem or did go away?
(Without more information I'll close the bug in a month.) cu andreas
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
