Subject: Re: correct "direction" of barriers in rc.d
To: Todd Vierling <tv@wasabisystems.com>
From: Andrew Brown <atatat@atatdot.net>
List: tech-userlevel
Date: 03/25/2002 13:07:04
>Let's say, for some freaky reason, that you need to force rpcbind to be
>started as part of NETWORK (the barrier dependency), so it startes before
>mountcritremote or somesuch, and don't want to edit any scripts.  Add a
>script:
>
>===== /etc/rc.d/LOCAL.force-rpcbind-NETWORK =====
># Dependency file to make rpcbind run as part of the NETWORK cluster.
>#
># REQUIRE: rpcbind
># BEFORE: NETWORK
>===== END =====
>
>Done!

not done.  :)

this gets me:

this# cat > /etc/rc.d/LOCAL.force-rpcbind-NETWORK << EOF
# Dependency file to make rpcbind run as part of the NETWORK cluster.
#
# REQUIRE: rpcbind
# BEFORE: NETWORK
EOF
this# rcorder -s nostart /etc/rc.d/*
...
rcorder: Circular dependency on provision `rpcbind' in file `/etc/rc.d/LOCAL.force-rpcbind-NETWORK'.
/etc/rc.d/LOCAL.force-rpcbind-NETWORK
...
/etc/rc.d/NETWORKING
...
/etc/rc.d/SERVERS
...
/etc/rc.d/rpcbind
...
this# rm /etc/rc.d/LOCAL.force-rpcbind-NETWORK 

you still have to tweak the rpcbind script so that it doesn't require
NETWORK.

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
andrew@crossbar.com       * "information is power -- share the wealth."