Andrew Howell writes ("Bug#1531: syslogd continues to write to old file after
savelog"):
> I just looked into this a little more. It seems that the /var/run
> file for syslog has changed. /etc/cron.weekly/sysklogd tries to
> do this.
>
> kill -1 `cat /var/run/syslog.pid`
I just looked into this a little more. It seems that the /var/run
file for syslog has changed. /etc/cron.weekly/sysklogd tries to
do this.
kill -1 `cat /var/run/syslog.pid`
but the file in /var/run is now this
-rw-r--r-- 1 root root3 Sep 28 13:53 syslogd.pid
Andrew
--
Package: syslogd
Version: 1.2-11
As you can see below the syslogd is still writing to daemon.0 after
savelog ran on Oct 1st.
-rw-r--r-- 1 root adm 0 Oct 1 06:47 /var/log/daemon
-rw-r--r-- 1 root adm207110 Oct 3 11:52 /var/log/daemon.0
root97 0.0 0.8
3 matches
Mail list logo
