Re: How to determine actual dependencies from within an init script?
Roy Marples
Wed Dec 02 19:16:43 2009
On Tuesday 01 December 2009 18:55:43 Hugo Mildenberger wrote:
> Sorry for not using bugs.marples.name as you indicated in your Readme file,
> but the name currently does not resolve. Similarily, your site does not
> indicate how to file a bug report (do I need an OpenID for doing that?)
Fixed the README.
You currently need OpenID, but I am evaluating moving all my projects into
Redmine as I've been suffering from a long problem with trac and pooled DB
connections not closing properly which my server is now struggling with.
> I would like to know if there is a runscript interface providing a service
> dependency list for a virtual service, which could be used from within an
> init script.
>
> Actually, you could call any script residing in /etc/init.d with parameters
> like "iuse", "ineed", "ibefore" and so on, but you can't do that for
> virtual services like "net" or "logger".
>
> Having such an interface available is of some interest with regard to
> firewall init scripts. E.g., one would prefer not to use a "logger"
> prerequisite, if the "logger" implementation actually depends on "net",
> or at least issue a strong warning about a likely misconfiguration.
>
> Alternatively, perhaps one could already test for named virtual
> dependencies?
We could add a --provides net feature to rc-status.
If I forget, open a bug :)
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.
Thanks
Roy
Archive administrator: postmaster@marples.name