openrc-discuss

Re: How to determine actual dependencies from within an init script?

Roy Marples

Wed Mar 17 20:46:06 2010

On Wed, 2010-03-17 at 11:41 +0100, Hugo Mildenberger wrote:
> Roy, may I remind :-) you to get rid of OpenID? 

No :)

> > 
> > However, you should remember that provided services are not always fixed and 
> > depend on the current state of the system, hence the option being against
> > rc-status.
> 
> I should have explained the root of the problem more clearly: runscript currently does 
> not handle contradictory dependencies consistently. E.g., Gentoo's shorewall rc 
> script should contain a "before net" dependency (it still does not). But it also contains 
> a dependency on a "logger" (or ulogd) service, which itself may add a "need net" 
> dependency, depending on the local configuration of the logging service.
> 
> A test with runscript from openrc-0.5.3 showed that runscript takes in account only 
> the last dependency instruction. If the depend()  function contains "before net" 
> immediately followed by "after net" instruction, the service would be always started 
> after net, and one does not even get a warning about this. runscript isn't excactly 
> wrong here. But normally you don't want a firewall to be started after the network, 
> especially if you thought to have told  openrc explicitely to run the associated scripts 
> the other way round.  
> 
> Here is a related Gentoo Bug: http://bugs.gentoo.org/show_bug.cgi?id=288992
> 

Not an OpenRC bug.
As "need, use and after" are all contradictory to before so we remove the
before depend. There is no ordering here, but if there was it would be like so

need > use > after > before

Thanks

Roy

Attachment: signature.asc
Description: This is a digitally signed message part


References:
How to determine actual dependencies from within an init script?Hugo Mildenberger
Re: How to determine actual dependencies from within an init script?Roy Marples
Re: How to determine actual dependencies from within an init script?Hugo Mildenberger
Archive administrator: postmaster@marples.name