Date: Sun, 01 Apr 2001 08:55:32 -0600 From: Wes Peters <wes@softweyr.com> To: David O'Brien <arch@FreeBSD.ORG> Cc: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>, Jack Rusher <jar@integratus.com>, Neil Blakey-Milner <nbm@mithrandr.moria.org>, Michael Lucas <mwlucas@blackhelicopters.org>, "litos2001@libero.it" <litos2001@libero.it> Subject: Re: Startup scripts a la NetBSD Message-ID: <3AC74164.252F2166@softweyr.com> References: <3AC4B808.9EB5806B@integratus.com> <200103301810.f2UIAGK06787@cwsys.cwsent.com> <20010330115252.A93566@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
David O'Brien wrote:
>
> On Fri, Mar 30, 2001 at 10:09:39AM -0800, Cy Schubert - ITSD Open Systems Group wrote:
> > Becoming more SYSV-like is not something most people in FreeBSD are
> > enamoured with. Hence I don't think it would be possible to implement
> > all the changes I would like to see.
>
> Correct. Make that HELL NO WE WON'T GO SVR4!!!
>
> The BSD init + NetBSD granular rc files is a nice compromise. And thus
> why I am pushing a move in that direction.
And is pretty much what I've done for DoBox. We start virtually every
server daemon on the box from an individual rc script. Ours handles
the usual start and stop arguments, as well as init, which is run only
during the very first system boot -- this allows packages that were
installed in the system image to complete their post-install phase.
We also have netstop and netstart dynamic events for when the internet
interface goes down and comes back up, so we can reconfigure firewall
settings, register dynamic dns, etc., if the IP address changes. We
have three events related to system backup: backup, pre-restore, and
post-restore, where subsystems can export data into a backup-able
format, stop servers, and restart servers and import restored data.
So far, it is working pretty well. I can't imagine trying to do
something like this by editing a single rc file. We run 'stop' and
'restore' events in reverse alpha order and all other events in
alphabetical order, making it simple to sequence the events. So far,
we have only two dependencies, both of which need to be started early
and stopped late, so we simply capitalized those two scripts and leave
the rest lower-case. Producing a sorted list from FreeBSD's multiple
rc.d directories is a simple enough process this shouldn't cause us
any problems.
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters Softweyr LLC
wes@softweyr.com http://softweyr.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3AC74164.252F2166>