BUG 12036: logwatch now starts at 00:05am to avoid conflicts with logrotate

Problem:
Every once in a while 'logwatch' creates an empty log file with 0 Bytes.

Probably 'logwatch' conflicts with the logrotate job which is
launched at the same time.

To avoid this in the future, the start of logwatch was postponed for
four minutes.

Signed-off-by: Matthias Fischer <matthias.fischer@ipfire.org>
Signed-off-by: Arne Fitzenreiter <arne_f@ipfire.org>

diff --git a/config/cron/crontab b/config/cron/crontab
index 4561f4a243239b8b5bd3525c067dc6a70395489c..56801394ece18abd19b2df5c324db30befa64c20 100644 (file)
--- a/config/cron/crontab
+++ b/config/cron/crontab
@@ -31,7 +31,7 @@ HOME=/
 */5 * * * *    [ -f "/var/ipfire/red/active" ] && /usr/bin/ddns update-all
 
 # Logwatch
-01 0 * * *     /usr/local/bin/logwatch > /var/log/logwatch/`date -I -d yesterday`; \
+05 0 * * *     /usr/local/bin/logwatch > /var/log/logwatch/`date -I -d yesterday`; \
                LOGWATCH_KEEP=$(sed -ne 's/^LOGWATCH_KEEP=\([0-9]\+\)$/\1/p' /var/ipfire/logging/settings); \
                find /var/log/logwatch/ -ctime +${LOGWATCH_KEEP=56} -exec rm -f '{}' ';'