Re: syslogd beserk (solved)
On Wed, 12 Nov 1997, E.L. Meijer (Eric) wrote:
> I think I found what caused it: I recently purged inn from the system.
> In the /etc/syslog.conf file there were lines about files that weren't
> there anymore:
> # Logging for INN news system
> news.crit /var/log/news/news.crit
> news.err /var/log/news/news.err
> news.notice -/var/log/news/news.notice
> After commenting the lines with news.* out, syslogd became its quiet
> self again. Now, isn't the postrm script from the inn package supposed
> to clean this up? Iow, is this a bug that I should report?
The bug has already been fixed in the later versions of syslog. No need
to report it.
Scott K. Ellis <email@example.com> http://www.gate.net/~storm/
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to firstname.lastname@example.org .