On Mon, 2009-12-14 at 11:16 +0100, edgar.sol...@web.de wrote: > > the syslog-ng manual also states > > page 38 [ details about klogd snipped ]
> 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." But then the FAQ contradicts this with it's "expanded syslog-ng.conf" (http://www.campin.net/syslog-ng/expanded-syslog-ng.conf) where it uses: source s_kernel { pipe("/proc/kmsg" log_prefix("kernel: ")); }; And then contradict themselves yet again with: * I want to replace syslogd *and* klogd on my Linux box with syslog-ng. Use a source line like this in your conf file to read kernel messages, too. source src { file("/proc/kmsg"); unix-stream("/dev/log"); internal(); }; in http://www.campin.net/syslog-ng/faq.html#klogd > therefore I am not sure if enabling logging kernel messages without > disabling klogd is a good idea. Of course. I don't use klogd here. Perhaps the packaging of syslog-ng should be such that it's mutually exclusive of whatever provides klogd, although I am not sure which package that is given that I don't use it here. :-) I'm also unsure if the ipk format allows the specification of "conflicts". > Also you should use file() and of course > add it to the log declaration. Well, the package authors themselves seem to use file and pipe with /proc/kmsg quite interchangeably. I think I'd like to see more clarification before I change what I think has been the historical use case. Of course, you can go ahead and submit a patch to change it yourself if you like, but using pipe() is working plenty fine here and I log plenty of kernel messages (i.e. every firewall exception and there are tons). b.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
