I'm looking at /etc/init.d/boot and /etc/init.d/syslog in Kamikaze. Both seem to start syslogd. /etc/init.d/boot does it in it's system_config() function:
system_config() {
...
config_get log_ip "$cfg" log_ip
# but what if we want to use syslog-ng here?
syslogd -C16 ${log_ip:+-L -R $log_ip}
klogd
}
and of course /etc/init.d/syslog's whole purpose is to start it.
How does this reconcile?
Why am I asking? Because I've opted to install syslog-ng onto my
Kamikaze router however I'm finding that I end up with both syslogd and
syslog-ng running, even though I've disabled the /etc/init.d/syslog
script (i.e. it is not linked into /etc/rc.d), which is obviously
because /etc/init.d/boot is starting it.
I could modify /etc/init.d/boot to start syslog-ng in preference to
syslogd if it's installed, but first I want to understand how having
syslogd started by both the boot and syslog scripts is reconciled.
Cheers,
b.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ openwrt-devel mailing list [email protected] http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
