On Mon, 20 May 1996, Lukas Nellen wrote:
> > "G" == Guy Maor <[EMAIL PROTECTED]> 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
> "G" == Guy Maor <[EMAIL PROTECTED]> 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
Guy Maor said:
> Package: syslogd
> Version: 1.3-2
> The bug is in syslogd - the last line of the /etc/cron.weekly/sysklogd
> script reads "/etc/init.d/sysklogd reload". Presumably this
> UNDOCUMENTED reload command has the same effect as sending a SIGHUP to
> syslogd. Except it doesn't.
I disa
Package: syslogd
Version: 1.3-2
Note to anyone that reples to this - check the headers, and don't cc to
debian-bugs if you aren't adding something useful.
> Files in /var/adm as daemon.log, messages, auth.log don't get updated this
> morning. Here's the rest of a ls -ltr in /var/adm
I think I kn
Files in /var/adm as daemon.log, messages, auth.log don't get updated this
morning. Here's the rest of a ls -ltr in /var/adm
-rw-r--r-- 1 root adm 0 May 19 06:47 daemon.log
-rw-r--r-- 1 root adm 0 May 19 06:47 debug
-rw-r--r-- 1 root adm 0 May
5 matches
Mail list logo