On Wed, Jan 22, 2003 at 03:44:44PM -0500, Dan Langille wrote:
> Yesteryday, killing and restarting syslogd solved the issue. But I'd
> rather investigate this before I do that today. Ideas?
this usually happens if you rotate (cp messages message.$DATE
&& cp /dev/null messages) a file syslog has
I have observed this behaviour today and yesterday. For some reason,
syslogd stops logging. Here's what I'm seeing:
[dan@undef:~/tmp] $ tail /var/log/messages
Jan 22 00:00:00 undef newsyslog[50185]: logfile turned over
[dan@undef:~/tmp] $ logger hi
[dan@undef:~/tmp] $ tail /var/lo
