On December 4, kor at compsoc.com said:
>> > I tried man logrotate, apparently it is configured via a file
> > specified on it's command line, but I have no idea of what in the
>> The config file should be /etc/logrotate.conf, which will then source
> scripts in /etc/logrotate.d/. Logrotate itself is likely run by cron,
> so have a quick look in /etc/cron.daily.
There's also some sort of cache file in /var/lib/logrotate.status
which is more likely to be the cause of your problems. I've run into
this in the past where logrotate has run amok and made several hundred
thousand backups of mailman logfiles, and recorded a line in the
status file for each one. Killing logrotate, deleting the file,
cleaning up /var/log by hand if necessary, then manually running
logrotate (and keeping an eye on it!) should clear the problem.
Cheers,
Waider.
--
waider at waider.ie / Yes, it /is/ very personal of me.
"When you say `I wrote a program that crashed Windows', people just stare
at you blankly and say `Hey, I got those with the system, *for free*'"
- Linus Torvalds
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
