All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rod Whitby <rod@whitby.id.au>
To: Paul Sokolovsky <pmiscml@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Adding sanity to OE startup process
Date: Wed, 11 Apr 2007 16:23:10 +0930	[thread overview]
Message-ID: <461C85D6.1010105@whitby.id.au> (raw)
In-Reply-To: <02429232.20070410152736@gmail.com>

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?

-- Rod



  reply	other threads:[~2007-04-11  6:54 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
2007-04-10 12:27   ` Paul Sokolovsky
2007-04-11  6:53     ` Rod Whitby [this message]
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=461C85D6.1010105@whitby.id.au \
    --to=rod@whitby.id.au \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=pmiscml@gmail.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 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.