RedShift wrote: > Jan de Groot wrote: >> On Sun, 2006-12-24 at 12:07 +0100, RedShift wrote: >>> Hello all >>> >>> I just uncovered some secret plot against me by the government. It >>> appears after logrotate runs every week, instead of logging continuing >>> with the newly logfiles, it continues to log to the rotated files! >>> >>> Example: >>> >>> we have auth.log >>> after logrotate this becomes auth.log.1 >>> a new empty file auth.log is created >>> logging continues on auth.log >>> >>> What's happening? >>> we have auth.log >>> after logrotate this becomes auth.log.1 >>> a new empty file auth.log is created >>> logging continues on auth.log.1 >>> auth.log remains empty. >>> >>> syslog-ng and logrotate configuration haven't been altered from the default. >>> >>> >>> Any ideas on how to resolve this? >> Yes, syslog-ng should get kicked after rotation. Without a kill -HUP it >> will keep the filedescriptors opened to the rotated file. >> > > But that's set up in > /etc/logrotate.d/syslog-ng > > all my other arch machines do it correctly, this one doesn't. >
Oh forget about it, found the problem. I store my httpd logs somewhere else, and logrotate quits prematurely because it can't find /var/log/httpd/*log Thanks, Glenn _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
