How to determine actual dependencies from within an init script?
Hugo Mildenberger
Tue Dec 01 18:57:56 2009
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?)
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?
Archive administrator: postmaster@marples.name