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

[Paul Sokolovsky]

Hello Rod,

Friday, April 6, 2007, 12:36:13 AM, you wrote:

> Paul Sokolovsky wrote:
>>   So, to start with, I'd like to propose to make it possible for boot
>> process to log to syslog. I have following in mind:
>> 
>> 4. Make /etc/init.d/syslogd.sh start earlier so it could capture as
>> mush output as possible.

> This is something that the syslog.file, syslog.buffer and syslog.network
> scripts in packages/slugos-init/files/initscripts try to do.  Syslog to
> buffer is started *as* *early* as possible.  Syslog to file is started
> as soon as filesystems are mounted, and Syslog to network is started as
> soon as the network is up.

> [I'm not suggesting you copy those files directly, or use the
> slugos-init package - this all needs to be generalised and subsumed into
> the standard init package as part of the slugos reincorporation into
> general OE.]

  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.

  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.)

[]

> -- Rod


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