[EMAIL PROTECTED] wrote:
> I just appended a line containing "*.* /dev/tty8" to /etc/syslog.conf, to let
> anything also beeing reported on tty8.
>
> After customizing /etc/syslog.conf, neither way to stop&start, restart or
> reload syslogd via /etc/init.d/sysklogd seems to work properly. /sbin/syslogd
> is running again, but no kernel messages are logged in any way. Logging from
> other processes like cron, backup-manager or sshd works.
>
> A complete system reboot helps, as does switching to runlevel 1 and then back
> to runlevel 2 via init. But neither option passed to /etc/init.d/sysklogd
> that involves stopping syslogd seems to get logging of kernel messages back
> up (dmesg still works, though).
Simply restarting klogd would have helped as well. When programs like
bind, inn, klogd lose connection to the system log daemon, they can't
log properly anymore and need to be restarted.
> After some tinkering around I found out that after a "/etc/init.d/sysklogd
> restart", a manual "/etc/init.d/klogd restart" reenables loggig of kernel
> messages. Is this intended behaviour?
It's at least the common behaviour.
Regards,
Joey
--
There are lies, statistics and benchmarks.
Please always Cc to me when replying to me on the lists.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
