Re: [Cooker] logrotate issue: runs forever
It should be fixed in the last release of sysklogd package, by replacing all global * (as in /var/log/daemons/*) in the syslog conf file placed in /etc/logrotate.d by explicit base names of log files. A patch had been applied to prevent logrotate from rotating compressed archives but that doesn't work. In fact the glob call that generates the files list to rotate don't use the banned extensions (they are only used for excludind configuration files), so if you use * (without any extension) it will initiate a rotation for each file of a directory, taking an exponential amount of time... Regards, Renaud
RE: [Cooker] logrotate issue: runs forever
logrotate stills runs "forever". something is
very wrong.
This was a known issue solved a while ago. The
problem lies in two sections of
/etc/logrotate.d/syslog beginning with:
/var/log/mail/*
and
/var/log/news/*
These lines rotate all the files in those
directories, including the files that have
already been rotated, which pretty much gets
stuck in an endless loop.
I went through and actually replaced those lines
with a line for each log file that needs to be
rotated:
/var/log/mail/mail.err {
rotate 5
weekly
postrotate
/usr/bin/killall -HUP syslogd
endscript
}
/var/log/mail/mail.warn {
rotate 5
weekly
postrotate
/usr/bin/killall -HUP syslogd
endscript
}
/var/log/mail/mail.info {
rotate 5
weekly
postrotate
/usr/bin/killall -HUP syslogd
endscript
}
/var/log/news/news.crit {
rotate 5
weekly
postrotate
/usr/bin/killall -HUP syslogd
endscript
}
/var/log/news/news.err {
rotate 5
weekly
postrotate
/usr/bin/killall -HUP syslogd
endscript
}
/var/log/news/news.notice {
rotate 5
weekly
postrotate
/usr/bin/killall -HUP syslogd
endscript
}
Don Head [[EMAIL PROTECTED]]
Linux Mentor, LCA, Network+ [1 314 692-1942]
Wave Technologies, Inc. [1 800 826-4640 x1942]
[AIM - Don Wave][ICQ - 18804935][Yahoo - Don_Wave]
Re: [Cooker] logrotate issue: runs forever
logrotate 3.3-8mdk (and 6mdk for that matter), run forever and never end. I have this set up as part of my /etc/cron.dailyRunning it with "-d" I get the "reading" the various configs and lots of disk I/O. logrotate is taking 94% of the CPU and 20% of memory. I had not noticed this until a few days ago when I had some very slow responses on the console. I had 3 running versions of logrotate. Presumably, the last the daily runs. What is going on? Could you give a listing of your /var/log/news directory? It made a huge mess of that directory on my box. To _remove_ /var/log/news (rm -rf /var/log/news) took about an hour... Stefan
Re: [Cooker] logrotate issue: runs forever
I am deleting /var/log/news as I type this. It is taking a while. I don't even run a news server and can't recall when I last looked in this directory. thx for the idea I'll see it this clears things up jim drash [EMAIL PROTECTED] Stefan van der Eijk wrote: logrotate 3.3-8mdk (and 6mdk for that matter), run forever and never end. I have this set up as part of my /etc/cron.dailyRunning it with "-d" I get the "reading" the various configs and lots of disk I/O. logrotate is taking 94% of the CPU and 20% of memory. I had not noticed this until a few days ago when I had some very slow responses on the console. I had 3 running versions of logrotate. Presumably, the last the daily runs. What is going on? Could you give a listing of your /var/log/news directory? It made a huge mess of that directory on my box. To _remove_ /var/log/news (rm -rf /var/log/news) took about an hour... Stefan
Re: [Cooker] logrotate issue: runs forever
logrotate stills runs "forever". something is very wrong. jdrash wrote: I am deleting /var/log/news as I type this. It is taking a while. I don't even run a news server and can't recall when I last looked in this directory. thx for the idea I'll see it this clears things up jim drash [EMAIL PROTECTED] Stefan van der Eijk wrote: logrotate 3.3-8mdk (and 6mdk for that matter), run forever and never end. I have this set up as part of my /etc/cron.dailyRunning it with "-d" I get the "reading" the various configs and lots of disk I/O. logrotate is taking 94% of the CPU and 20% of memory. I had not noticed this until a few days ago when I had some very slow responses on the console. I had 3 running versions of logrotate. Presumably, the last the daily runs. What is going on? Could you give a listing of your /var/log/news directory? It made a huge mess of that directory on my box. To _remove_ /var/log/news (rm -rf /var/log/news) took about an hour... Stefan
