Hi all, I was wondering, sysklogd has two daemons - one for syslogs, and one for kernel logs. Does syslog-ng handle both facilities, or am I missing out on the kernel logs that would be done by klogd? Is there any way to get all of the same logging that I was getting provided by sysklogd? I have read what documentation I can find, but am still a bit confused - obviously. Thanks. geoffrey -- +++++++++++++++++++++++++++++++++++++++++++++++++++ "There really isn't much value in free." -- Doug Miller MS group product manager for competitive strategies +++++++++++++++++++++++++++++++++++++++++++++++++++
I was wondering, sysklogd has two daemons - one for syslogs, and one for kernel logs. Does syslog-ng handle both facilities, or am I missing out on the kernel logs that would be done by klogd? Is there any way to get all of the same logging that I was getting provided by sysklogd? I have read what documentation I can find, but am still a bit confused - obviously. Thanks.
syslogd and klogd are two separate daemons. if you want kernel logs to be outputted you'll need to have klogd running as well. I wrote a syslog-ng startup (sys-v style) script for red hat linux systems - it should work more or less on most distros. it starts klogd then syslog-ng. -sv
On Fri, 25 May 2001, Seth Vidal wrote:
I was wondering, sysklogd has two daemons - one for syslogs, and one for kernel logs. Does syslog-ng handle both facilities, or am I missing out on the kernel logs that would be done by klogd? Is there any way to get all of the same logging that I was getting provided by sysklogd? I have read what documentation I can find, but am still a bit confused - obviously. Thanks.
syslogd and klogd are two separate daemons.
if you want kernel logs to be outputted you'll need to have klogd running as well.
I wrote a syslog-ng startup (sys-v style) script for red hat linux systems - it should work more or less on most distros.
it starts klogd then syslog-ng.
Not true without clarification. syslog-ng can be configured to read kernel messages with source kernel_file { file("/proc/kmsg"); }; If you have klogd running and read kernel messages with syslong-ng they will block each other and nevermind logging, it stops as they deadlock on the file descriptor. I fought this for a while. Brian Seppanen seppy@chartermi.net
Not true without clarification. syslog-ng can be configured to read kernel messages with
source kernel_file { file("/proc/kmsg"); };
didn't know that. I don't know if I like it though :/
If you have klogd running and read kernel messages with syslong-ng they will block each other and nevermind logging, it stops as they deadlock on the file descriptor.
I fought this for a while.
I tend to like treating syslog-ng as a replacement for syslogd and not for both. but thanks for the tip. -sv
I was wondering, sysklogd has two daemons - one for syslogs, and one for kernel logs. Does syslog-ng handle both facilities, or am I missing out on the kernel logs that would be done by klogd? Is there any way to get all of the same logging that I was getting provided by sysklogd? I have read what documentation I can find, but am still a bit confused - obviously. Thanks.
syslogd and klogd are two separate daemons.
if you want kernel logs to be outputted you'll need to have klogd running as well.
I wrote a syslog-ng startup (sys-v style) script for red hat linux systems - it should work more or less on most distros.
it starts klogd then syslog-ng.
-sv
On linux: source kern { file("/proc/kmsg"); }; No syslogd or klogd. Cheers! -- A.L.Lambert ------------------------------------------------------------------------ The problems that exist in the world today cannot be solved by the level of thinking that created them... -Einstein ------------------------------------------------------------------------
participants (4)
-
A.L.Lambert
-
Brian E. Seppanen
-
geoffrey
-
Seth Vidal