On Tue, Jun 04, 2002 at 03:51:45PM -0400, Jameson C. Burt wrote: > I installed the package "syslog-ng", replacing the package "sysklogd". > After this, my kernel logs (including my "iptables" logs) no longer > went to /var/log/{kern,debug,messages}, or any other file in /var/log. > Syslog-ng would log the usual daemon messages. > After spending 5 hours alterning the new /etc/syslog-ng/syslog-ng.conf, > I saw that my Debian Linux needed only a reboot [aka Windows]. > Actually, I didn't reboot, I ran > /etc/rc2.d/S10syslog-ng stop > /etc/rc2.d/S11klogd stop > /etc/rc2.d/S10syslog-ng start > /etc/rc2.d/S11klogd start > > Normally, one would restart these in /etc/init.d, > which I had been futily doing, but the start order > seemed necessary from /etc/rc2.d . > The two packages syslog-ng [or sysklogd] and klogd, > as the documentation says, work closely with each other. > The package klogd sends kernel logs > (including my wanted iptables firewall logs) to the syslog daemon.
I had the same problem (no kernel messages) - restarting sysklogd and klogd in this order solves the problem. I did it with rc2.d *and* with init.d on two different machines and *both* worked. Thanks for this tip :-) Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]