On 02/01/12 14:20, Saul Wold wrote:
On 01/02/2012 01:50 PM, Joshua Lock wrote:
Busybox 1.19 introduced basic support for an rsyslog inspired syslog.conf
whereas we've been shipping syslog.conf as a file to be sourced by the
syslog init script in order to configure which options busybox's
syslog is
started with.
Busybox 1.19 in syslog mode chokes on our syslog.conf and doesn't start.
This patch renames the syslog.conf we ship to syslog-startup.conf in
order
to prevent busybox trying to parse the file as an rsyslog style
syslog.conf
Do we need to also add an updated skeleton syslog.conf that the busybox
syslog can parse?
We certainly could do that, but there's no need to. The syslog.conf is
optional and the options we set at init continue to work as they have.
In fact, as far as I could tell from a quick search this morning,
there's no way to tell syslogd log to a buffer, as we currently do by
default, with syslog.conf.
Cheers,
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
