Hi Brian, 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.
Cheers, D. On 12/28/2012 03:18 PM, Brian J. Murrell wrote: > I have installed syslog-ng3, configured it and started it. I notice > that while it does seem to be doing the work of logging to my syslog > server, the old syslogd still seems to be running. > > Should the installation and/or startup of syslog-ng[3] either prevent > the standard syslogd from running or at least kill it once syslog-ng[3] > starts taking over? > > Cheers, > b. > > > > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
