[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[leafnode-list] Re: logrotate, sysklogd, news logs (again).
Am Samstag, den 22.12.2007, 09:12 +0000 schrieb Adam Funk:
> I upgraded a computer from Ubuntu Feisty to Gutsy recently and then
> ran into the "not logging through syslog" problem described in a
> previous thread. [1]
>
>
> So I edited /etc/logrotate.d/leafnode and changed this (the last
> stanza)
>
> /var/log/news/news.info {
> daily
> rotate 5
> compress
> missingok
> }
>
> to this
>
> /var/log/news/news.info {
> daily
> rotate 5
> compress
> missingok
> sharedscripts
> postrotate
> kill -1 $(cat /var/run/syslogd.pid)
> endscript
> }
>
>
> That didn't work, so I added the same four lines to the entries for
> news.crit, news.err and news.notice in the same file. I believe the
> kill -1 is SIGHUPping the daemon because I see
> syslogd 1.4.1#21ubuntu3: restart.
> entries in the syslog at the time of the log rotation.
>
>
> I believe my cron.daily is carrying out logrotate before the sysklogd
> script (which rotates syslog and restarts the daemon again).
>
> Any further debugging suggestions?
Hi Adam,
how does your /etc/syslog.conf look like?
The one on my Mom's computer (also upgraded from Feisty Fawn to Gusty
Gibbon) contains these lines - this is unrelated to the upgrade though.
# 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
That is, there is no news.info logging at all, and notice logging is
deliberately scarcer (it's a higher severity) than info.
You can of course add a news.info line or replace the news.notice line
to have news.info logged, and you'll want to accompany that by the first
logrotate.d/leafnode block you've shown above.
HTH
Matthias
--
_______________________________________________
leafnode-list mailing list
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
https://www.dt.e-technik.uni-dortmund.de/mailman/listinfo/leafnode-list
http://leafnode.sourceforge.net/