Bug#3188: sysklogd still logs to *.0 files

[Dirk.Eddelbuettel@qed.econ.queensu.ca]

This message might be related to the problem with sysklogd-1.3-6 still
logging to files foobar.0 instead of foobar in /var/adm.

    From: root (Cron Daemon)
    To: root
    Subject: Cron <root@miles> run-parts /etc/cron.weekly
    Date: Sun, 2 Jun 96 06:47 EDT

    Restarting.. httpd
    Sending..... HUP signal to process 2312
    cat: /var/run/syslog.pid: No such file or directory
    run-parts: /etc/cron.weekly/sysklogd exited with return code 1


--
Dirk Eddelb"uttel                             http://qed.econ.queensu.ca/~edd