From: Joshua Lock <josh@linux.intel.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] busybox: rename syslog.conf to syslog-startup.conf
Date: Mon, 02 Jan 2012 15:11:40 -0800 [thread overview]
Message-ID: <4F0239AC.2050100@linux.intel.com> (raw)
In-Reply-To: <4F022DB5.3040501@linux.intel.com>
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
next prev parent reply other threads:[~2012-01-02 23:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 21:50 [PATCH] busybox: rename syslog.conf to syslog-startup.conf Joshua Lock
2012-01-02 22:20 ` Saul Wold
2012-01-02 23:11 ` Joshua Lock [this message]
2012-01-03 20:06 ` Anders Darander
2012-01-04 12:03 ` Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F0239AC.2050100@linux.intel.com \
--to=josh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox