[oe] [RFC] Adding sanity to OE startup process

[Paul Sokolovsky]

Hello Rod,

Wednesday, April 11, 2007, 9:53:10 AM, you wrote:

> Paul Sokolovsky wrote:
>>   I expected SlugOS project to be important stakeholder for such
>> changes, so I appreciate your response, Rob! I had a look at
>> slugos-init's syslog handling, and for sure it looks well done and
>> should be generalized to the whole OE.

> Thanks.  It was mostly done by John Bowler.  Any bugs introduced since
> then are my responsibility :-)

>>   I guess, at this point, I should just play with it to understand
>> how it works better (for example, a question I have in mind: each of
>> syslog.{buffer, file, network} appears to just run syslogd with new
>> commandline params, not restart it or send signal; is this reliable
>> (e.g. documented)? Well, as I tell, I should try it myself first I
>> guess.)

> Good question.  I thought that only *one* of them would get started,
> based on the contents of the destination field in /etc/sysconf.conf at
> boot.  Is that not what you're seeing?

        Sorry, for delay, due to approaching of 2.6.22 merge window, I
work mostly on HH.org kernel now, but yesterday finally found time to
play with this issue.

        So yes, I see that the idea after all is log to only one
destination, just start logging as soon as possible for that
destination. I just had in mind something what Koen mentioned: start
logging to buffer ASAP, then later switchover to file if needed, then
to network if needed. Well, that's of course more of advanced feature.

        Also, confirmed that file log rotation works at least with
busybox 1.2.1. Cleaned up syslogd.conf fixed to not contain confusing
statements this is not supported, committed. Koen, what do you think
about switching Angstrom's default setting to /var/log/messages after
this, to make it easier for non-busybox people? After all, main
trouble with file logging is now fixed - it cannot grow unlimited in
size.


> -- Rod


-- 
Best regards,
 Paul                            mailto:pmiscml at gmail.com