I have stopped using klogd. Here is what have done instead. source src { unix-stream("/dev/log"); internal(); pipe("/proc/kmsg"); }; I have had no issues. ----- Original Message ----- From: "Victor" <victord@paid.com> To: <syslog-ng@lists.balabit.hu> Sent: Friday, April 26, 2002 2:16 PM Subject: Re: [syslog-ng]Iptables is not logging to sysylog-ng
-----Original Message----- From: syslog-ng-admin@lists.balabit.hu [mailto:syslog-ng-admin@lists.balabit.hu]On Behalf Of Michael Renner Sent: Friday, April 26, 2002 11:28 AM To: syslog-ng@lists.balabit.hu Subject: RE: [syslog-ng]Iptables is not logging to sysylog-ng
At 11:12 26.04.2002 -0400, you wrote:
It WORKED!!!!
I put the --file("/proc/kmsg");-- entry on syslog-ng.conf and ran the klogd with the -c 1 option..
Uhh, this was supposed to be a exclusive or, either syslog-ng with /proc/kmsg source OR klogd, both won't work because /proc/kmsg is a fifo (stuff disappears from it after it has been read).
mfg/best regards
--
Michael Renner Junior System Engineer
What exactly does klogd do? was it separated from syslogd for Licensing issues? Is it safe to replace klogd with --file("/proc/kmsg"); ? Also, can you give an example of actual config that has this?
Thanks a bunch
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng