Subject: Re: correct "direction" of barriers in rc.d
To: David Laight <firstname.lastname@example.org>
From: Todd Vierling <email@example.com>
Date: 03/20/2002 15:37:57
On Wed, 20 Mar 2002, David Laight wrote:
: > And if db X is from pkgsrc, or from a third-party vendor? Is anything
: > not from the base system considered "local" in that the admin is
: > expected to have to hack on it for such things?
: Seems like an 'AFTER' tag would do - one that doesn't require
: the referenced script to be present.
Why would you not require it to be present, if you have the full knowledge
that you're gluing a database into rc.d?
: Then you could add a dummy script that just contained:
: # AFTER: xxx
: # BEFORE: yyy
BEFORE requires its entries to be present. In fact, the whole rcorder/rc.d
system expects no dangling dependencies; a warning is issued if there are
Given that you'd expect both entries in the above to be present (in the case
of "run db X before inetd", you can still have a dummy glue script, and
simply replace AFTER with REQUIRE. Done.
-- Todd Vierling <firstname.lastname@example.org> * Wasabi & NetBSD: Run with it.
-- CDs, Integration, Embedding, Support -- http://www.wasabisystems.com/