On Wed, 20 Nov 1996, Branden Robinson wrote:
> ./etc/init.d/sysklogd restart; ps -ax | grep syslogd; ps -ax | grep klogd
>
quick tip (totally unrelated to the syslogd problem, but useful anyway):
instead of the above line, use
./etc/init.d/sysklogd restart; ps -axc | grep syslogd\\\|klogd
On Wed, 20 Nov 1996, Branden Robinson wrote:
> I have a similar problem (but I can eventually get syslogd and klogd to
> both come up by "./etc/init.d/sysklogd restart" over and over again). I
> did a test -e for every file mentioned in /etc/syslog.conf and got a 0
> status every time?
>
> Does
> Look in /etc/syslog.conf, and make sure all of the log files mentioned in
> that file, and their _directories_, actually exist. I hear stories of this
> happening when removing some package, because the log file and its directory
> disappears, and syslogd gets into a loop trying to open the log f
> As of last Thursday I have been encountering problems with the syslog
> daemon. I have posted to various newsgroups but have not received any answer
> so far.
> After booting the system, the syslog daemon seems to be dying. Whenever I
> reboot the system the messages will state
> starting /sbi
Look in /etc/syslog.conf, and make sure all of the log files mentioned in
that file, and their _directories_, actually exist. I hear stories of this
happening when removing some package, because the log file and its directory
disappears, and syslogd gets into a loop trying to open the log file.
5 matches
Mail list logo