tech-userlevel archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: syslog message with wrong date, and patch for newsyslog

In article <>,
Jeremy C. Reed <> wrote:
>My syslog had been dead for a few days. (I saw some cronjob mail about 
>newsyslog unable to kill.)
>Today I looked at some logs and saw no updates for a week. So I saw 
>syslogd not running. I started it and immediately logged:
>Jan 12 09:08:29 t1 syslogd[17678]: restart
>Jan 12 09:08:29 t1 /netbsd: UVM: pid 4690 (vi), uid 1000 killed: out of 
>Jan 12 09:08:29 t1 /netbsd: UVM: pid 156 (syslogd), uid 0 killed: out of 
>(I know this vi crash was due to editing with vi -r. I am pretty sure 
>this is fixed now but cannot find the gnats ticket number.)
>So the last two messages with today's timestamps really happened maybe 
>on January 6.
>By the way, a couple days ago I updated my newsyslog with:

Ok, but if you are going to touch this, please change all sys_signame[]
references to strsignal(3)...


Home | Main Index | Thread Index | Old Index