All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rod Whitby <rod@whitby.id.au>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Adding sanity to OE startup process
Date: Fri, 06 Apr 2007 07:37:29 +0930	[thread overview]
Message-ID: <46157321.1050607@whitby.id.au> (raw)
In-Reply-To: <46156E12.9090002@dominion.kabel.utwente.nl>

Koen Kooi wrote:
> Rod Whitby schreef:
>>> 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.
> 
> Sounds pretty neat, does the buffer get flushed to file as well?

At the moment, no.  You get to choose the destination in
/etc/syslog.conf, and it only logs to that destination.

(e.g. if you need early debugging, you have to set it to buffer)

-- Rod



  reply	other threads:[~2007-04-05 22:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-05 15:27 [RFC] Adding sanity to OE startup process Paul Sokolovsky
2007-04-05 15:33 ` Sergey Lapin
2007-04-05 15:49   ` Paul Sokolovsky
2007-04-05 21:36 ` Rod Whitby
2007-04-05 21:45   ` Koen Kooi
2007-04-05 22:07     ` Rod Whitby [this message]
2007-04-10 12:27   ` Paul Sokolovsky
2007-04-11  6:53     ` Rod Whitby
2007-04-23  7:15       ` Paul Sokolovsky
2007-04-23  7:59         ` Koen Kooi
2007-04-24 12:26           ` Paul Sokolovsky
2007-04-10 11:27 ` Michael 'Mickey' Lauer

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=46157321.1050607@whitby.id.au \
    --to=rod@whitby.id.au \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.