Date: Sat, 11 Nov 2000 09:30:18 -0700 From: Wes Peters <wes@softweyr.com> To: Jan Grant <Jan.Grant@bristol.ac.uk> Cc: Greg Black <gjb@gbch.net>, Christoph Sold <so@server.i-clue.de>, Jimmy Olgeni <olgeni@uli.it>, hackers@FreeBSD.ORG Subject: Re: What about rc.shutdown.local? Message-ID: <3A0D741A.5D50F8CF@softweyr.com> References: <Pine.GSO.4.21.0011111034001.1850-100000@mail.ilrt.bris.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Jan Grant wrote:
>
> On Sat, 11 Nov 2000, Greg Black wrote:
>
> > Jan Grant writes:
> >
> > > > Better still would be /usr/local/etc/rc.d/*.sh called automatically
> > > > with parameter stop. To do so, insert
> > >
> > > This is all nice (BTDT) although I find the *.sh pattern quite annoying,
> > > due to the alphabetisation issue. When I make these mods I tend to use
> > > the SysV-style S* and K* patterns - that means you get to control the
> > > order of startup _and_ shutdown (which might need a different sequence).
> >
> > This seems trivial. I name the scripts with two-digit prefixes
> > and an underscore so that I can have meaningful names and an
> > easy way to control the sequence.
>
> It _is_ trivial, but you miss my point: I run several things at startup
> that rely on a database service (which needs to be launched first). When
> they shut down, the DB must still be running (it's taken down last). So
> using a *.sh pattern for startup and shutdown scripts doesn't satisfy my
> requirements.
make? tsort?
This was discussed ad nauseum in the last round of discussions about
replacing /etc/rc*, search the archives if you're interested.
--
"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-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A0D741A.5D50F8CF>