From: Roy Marples <roy@marples.name>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Baselayout-2 progress?
Date: Sat, 1 Mar 2008 00:56:54 +0000 [thread overview]
Message-ID: <200803010056.54037.roy@marples.name> (raw)
In-Reply-To: <47C893F6.4090905@wildgooses.com>
On Friday 29 February 2008 23:23:34 Ed Wildgoose wrote:
> > [2] I use busybox as a shell and can support it when it's internal
> > start-stop-daemon applet disabled (as OpenRC has it's own variant).
>
> I guess I could just check it out instead of asking but.... What's
> missing from the busybox s-s-daemon?
>
> I am using the busybox version 95% successfully with baselayout-2 for
> example (just simple stuff mind). The only thing it's breaking on right
> now is a --test option which doesn't seem to exist?
>
> I'm not that fussed, I'm just curious?
s-s-d when used in an OpenRC service remembers how the daemon is started so it
can poll to see if it's still running or not. We also use this ability to
ensure the daemon really starts. A lot of daemons love to fork (and return
success) before checking config and system for sanity, so sometimes it's
needed.
OpenRC variant also works better for finding daemons on the whole, especially
if you upgrade an already running daemon.
Plus, it supports more OS's than busybox - but to be fair, busybox only
supports Linux.
It's also missing chroot and env options from the upstream Debian version.
It's also missing the Gentoo extras for PAM limits support and redirecting the
daemons stdout/stderr to log files.
It also requires the crappy use of oknodo.
It fails to search for daemon arguments when stopping (important for say
daemons using python without pidfiles)
I'm not sure that busybox would take any patches to add much of the above as
most would add more bloat for sure.
Thanks
Roy
--
gentoo-dev@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-03-01 0:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 14:12 [gentoo-dev] Baselayout-2 progress? Ed W
2008-02-29 14:16 ` Alon Bar-Lev
2008-02-29 15:56 ` Ed W
2008-02-29 16:02 ` Doug Klima
2008-02-29 16:15 ` Ed W
2008-02-29 16:30 ` Doug Klima
2008-02-29 17:07 ` Roy Marples
2008-02-29 18:32 ` Stefan Hellermann
2008-02-29 19:45 ` Roy Marples
2008-02-29 19:57 ` Stefan Hellermann
2008-02-29 20:15 ` Doug Klima
2008-02-29 20:31 ` Stefan Hellermann
2008-02-29 23:17 ` Ed Wildgoose
2008-03-01 2:08 ` [gentoo-dev] " Duncan
2008-03-01 4:59 ` Doug Klima
2008-03-01 5:04 ` [gentoo-dev] Re: Blockers (was: Baselayout-2 progress?) Ciaran McCreesh
2008-03-01 9:49 ` [gentoo-dev] Re: Baselayout-2 progress? Duncan
2008-03-01 10:50 ` Roy Marles
2008-03-01 19:17 ` Duncan
2008-03-01 22:50 ` [gentoo-dev] " Bernd Steinhauser
2008-03-01 23:42 ` [gentoo-dev] " Duncan
2008-03-02 0:55 ` Bernd Steinhauser
2008-02-29 17:01 ` [gentoo-dev] " Roy Marples
2008-02-29 17:50 ` Benedikt Boehm
2008-02-29 23:19 ` Ed Wildgoose
2008-02-29 23:23 ` Ed Wildgoose
2008-03-01 0:56 ` Roy Marples [this message]
2008-03-01 22:26 ` Ed W
2008-03-01 22:29 ` Roy Marples
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=200803010056.54037.roy@marples.name \
--to=roy@marples.name \
--cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox