> The problem is that those barrier dependencies don't *actually*
> require anything, but rather all the things listed in their REQUIRE
> lines simply need to be started before the barrier.  Therefore, it
> seems logical that rather than listing those things as REQUIRE, the
> individual scripts that want to be started before some barrier should
> list that barrier in a BEFORE statement.

That sounds reasonable to me.

However, what about ordering requirements that are not an attribute of
either script involved, but rather of some decision the system's
administrator has made?  (I'm thinking things like "we want db X to be
up before starting inetd, because inetd has an entry that accesses that
db".)  It seems to me there is presently nowhere to declare such
dependencies that's conceptually right.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B