you are right vasilis .. I just tried it with syslog-ng3 ..
the syslog-ng manual also states
page 38
"On Linux, the klogd daemon can be used in addition to syslog-ng to read
kernel messages and forward them to syslog-ng.
klogd used to preprocess kernel messages to resolve symbols etc., but as
this is deprecated by ksymoops there is really
no point in running both klogd and syslog-ng in parallel. Also note that
running two processes reading /proc/kmsg at
the same time might result in dead-locks.
When using syslog-ng to read messages from the /proc/kmsg file,
syslog-ng automatically disables the follow_freq()
parameter to avoid blocking the file."
and about the use of pipe on Page 39
"Pipe is very similar to the file() driver, but there are a few
differences, for example pipe() opens its argument
in read-write mode, therefore it is not recommended to be used on
special files like /proc/kmsg."
therefore I am not sure if enabling logging kernel messages without
disabling klogd is a good idea. Also you should use file() and of course
add it to the log declaration.
... ede
On 14.12.2009 09:41, Vasilis Tsiligiannis wrote:
Hello Brian,
-log { source(src); destination(messages); };
+log { source(src); source(kernel); destination(syslog_server); };
Correct me if I am wrong: shouldn't there be a "destination syslog_server
{...};" also present in the config? Or just send them to messages destination
which already exists?
Best Regards,
Vasilis Tsiligiannis
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
