Re: Bug#3072: No more logs since cron.weekly rotation
On Mon, 20 May 1996, Lukas Nellen wrote:
> >>>>> "G" == Guy Maor <firstname.lastname@example.org> writes:
> G> The bug is in syslogd - the last line of the /etc/cron.weekly/sysklogd
> G> script reads "/etc/init.d/sysklogd reload". Presumably this
> G> UNDOCUMENTED reload command has the same effect as sending a SIGHUP to
> G> syslogd. Except it doesn't.
> This is related to another bug reported (can't find the number right
> now) in that start-stop-daemon cannot read the pid of syslogd from the
> pid file. This manifests itself also during shutdown - the K-links for
> syslogd fail to kill syslogd. Something seems to be wrong with the way
> that syslogd writes its pid file.
Very wrong? Yes and no. The problem was that syslogd wrote its pid file as
syslog.pid (no 'd'). It's been fixed in sysklogd-1.3-3.