On 12-12-29 05:23 AM, Daniel A. Nagy wrote: > Hi Brian, Hi Daniel!
> The builtin syslogd "logs" to a circular buffer in RAM. It is fairly > failsafe and does not take up many resources. I think that the current > behavior of leaving it running upon installation of more heavyweight > syslog services is correct behavior. Interesting perspective. The reason it seemed so important here to shut it down was because I had configured it to forward to a syslog server here and then also configured syslog-ng3 to do the same. Of course that was not a good situation. But indeed, simply reverting the configuration of having the built-in syslogd log to the syslog server serves my purposes as well. But what about slurping up the kernel messages, (i.e. /proc/kmesg)? Can the built-in syslogd/klogd and syslog-ng3 both read from those or will it be racy with the first reader consuming them and the second reader not getting any? Cheers, b.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
