Re: Error message from cron, regarding "newsyslog"

[Kjell Wooding <kwooding@codetalker.com>]

I had the same problem once. Theo suspected it was a parity problem. (the PID logged in the /var/run/syslog.pid file was different from the ps list by a single bit.)  

Since it was such an oddity, I tended to agree.

IT is a bit odd, though, as it was the same process in both cases. (mine was also syslogd)

Check the syslog.pid file, and see if it is a bit flip away from the value that ps reports...

At 07:23 PM 1/4/99 +0100, Needlejaw wrote:
>Hi,
>
>Every so often for the past week or so I've gotten the following mail from
>crontab:
>
>>From root Mon Jan  4 20:00:01 1999
>From: root (Cron Daemon)
>To: root
>Subject: Cron <root@prime> /usr/bin/newsyslog
>X-Cron-Env: <SHELL=/bin/sh>
>X-Cron-Env: <PATH=/bin:/sbin:/usr/bin:/usr/sbin>
>X-Cron-Env: <HOME=/var/log>
>X-Cron-Env: <LOGNAME=root>
>X-Cron-Env: <USER=root>
>
>newsyslog: preposterous process number: 40984
>
>--
>
>ps -p reports this:
>
>bash-2.02$ ps -p 40984
>  PID TT   STAT      TIME COMMAND
>40984 ??  Is      0:00.70 syslogd -a /var/named/dev/log
>
>--
>
>uname -a is : OpenBSD prime 2.4 ANTIFISH#7 i386
>
>--
>
>I'm not sure what caused this, as it seemed to "just appear" one day.
>(Incidentally, right after I had cvsup'ed the kernel sources and rebooted
>because of a new kernel config. The box hasn't been booted since.)
>I've just tried restarting syslogd, but I guess I won't know till tomorrow
>if that fixed it. I'm curious, though, what might have caused it.
>
>Any input would be welcome. :-)
>
>Thanks for your time,
>
>Jo B.
>
>--
>"People will pay big bucks for the luxury of ignorance."