I've been using syslogd-ng for quite a while now... like it a lot! Just installed the latest stable version on a new system and now I see a strange behaviour: I installed syslogd-ng. He's logging just fine but then I realized that I don't get any klogd messages!! Not even when klogd comes up! Using the standard syslogd works just fine... Where's the problem? -- Torsten
I've been using syslogd-ng for quite a while now... like it a lot! Just installed the latest stable version on a new system and now I see a strange behaviour:
I installed syslogd-ng. He's logging just fine but then I realized that I don't get any klogd messages!! Not even when klogd comes up! Using the standard syslogd works just fine...
Where's the problem? -- Torsten
Dunno what problem, but know a possible solution. Just have syslog-ng read /proc/kmsg, and it'll do same job as klogd, and don't run klogd anymore. Cheers. --A.L.
Where's the problem? -- Torsten
Dunno what problem, but know a possible solution. Just have syslog-ng read /proc/kmsg, and it'll do same job as klogd, and don't run klogd anymore. Cheers.
Hm.. worked thanks... but I really would like to know where the problem was... puzzled -- Torsten
Where's the problem? -- Torsten
Dunno what problem, but know a possible solution. Just have syslog-ng read /proc/kmsg, and it'll do same job as klogd, and don't run klogd anymore. Cheers.
Hm.. worked thanks... but I really would like to know where the problem was...
puzzled
Hehe. me too. I never did figure out problem; but figured out solution, so next best thing. Too much work; not enough time to "tweak" stuff and figure out what's doing what and (more importantly) _WHY_. :) Anyhoo... --A.L.Lambert
Dunno what problem, but know a possible solution. Just have syslog-ng read /proc/kmsg, and it'll do same job as klogd, and don't run klogd anymore. Cheers.
Hm.. worked thanks... but I really would like to know where the problem was...
puzzled
Hehe. me too. I never did figure out problem; but figured out solution, so next best thing. Too much work; not enough time to "tweak" stuff and figure out what's doing what and (more importantly) _WHY_. :) Anyhoo...
an strace dump of klogd may shed some light to the problem. klogd and syslog-ng interoperates flawlessly. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt
I've been using syslogd-ng for quite a while now... like it a lot! Just installed the latest stable version on a new system and now I see a strange behaviour:
I installed syslogd-ng. He's logging just fine but then I realized that I don't get any klogd messages!! Not even when klogd comes up! Using the standard syslogd works just fine...
1) klogd may start earlier than syslog-ng, it doesn't like it 2) klogd is trying to send messages using SOCK_DGRAM style, you should then use unix-dgram instead of unix-stream() -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt
I installed syslogd-ng. He's logging just fine but then I realized that I don't get any klogd messages!! Not even when klogd comes up! Using the standard syslogd works just fine...
1) klogd may start earlier than syslog-ng, it doesn't like it 2) klogd is trying to send messages using SOCK_DGRAM style, you should then use unix-dgram instead of unix-stream()
1)I tried to start 'em by hand... so I'm sure klogd came after syslog-ng! 2) what is the diffence... I guess unix-dgram uses a port and unix-stream a pipe? Well, using a the /proc/kmsg pipe worked for me... Any further ideas though? -- Torsten
participants (3)
-
A.L.
-
Balazs Scheidler
-
Torsten Curdt