On Tuesday 10 May 2005 9:03 pm, Stuart Bailey wrote:
Googling seems to suggest that ssyslogd needs a config file (/etc/syslog.conf). Unfortunately, the syslogd I'm using comes as part of busybox, and it ignores /etc/syslog.conf.
Ahh that would be a bit of a problem. Looks horribly like a rebuild of busybox may be in order to me.
Or perhaps try calling syslogd with the -K option (assuming all the messages are bothering you are comming from the kernel) but then of course that is a bit of a bodge because now you have no kernel logging. The -K option seems to be unique to the busybox version of syslogd BTW