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

From: [email-masked]
Date: Sun, 2 Jun 96 17:17 EDT

Package: sysklogd
Version: 1.3-6

Some time last week I upgraded from sysklogd-1.3-4 to sysklogd-1.3-6. The
upgrade went smoothly, and I did not change any config files.

After the file rotation induced by cron.weekly this morning, logs are written
to the the foobar.0 files instead of to foobar.

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

---

From: [email-masked]
Date: Mon, 3 Jun 96 09:47 EDT

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