Package: base Severity: important Debian stable and testing come with logrotate, which appears to be a centralised way to configure log rotation. However, if you edit the logrotate.conf (and logrotate.d/*) to only do monthly rotations, you will find inconsistent results in /var/log. Some logs are rotated monthly, others appears to be rotated daily.
Turns out, there are still multiple log rotation facilities installed and configured in a standard Debian install. There's logrotate and various scripts under /etc/cron.daily and /etc/cron.weekly that also do logrotation (the worst offender is /etc/cron.*/syslogd which uses savelog). Why hasn't all this been cleared up and all log rotation done centrally via logrotate? And why does every single package that installs a logrotate script into /etc/logrotate.d include directives for compression and rotation period? These are configured globally via /etc/logroate.conf. As it is now, it takes almost an hour to find all the places where logrotation happens and make it all consisten across the entire system. Spreading that across multiple systems, it can take an entire day or more to get things working consistently across a server room. Also, why is it that the defaults rotate the logs on a daily or even weekly basis? It makes it very hard to do searches in the log files. Please consider changing the defaults to monthly rotation. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.15-1-k7-smp Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
