Re: chkconfig for Debian
On Mon, Dec 10, 2001 at 02:27:56PM +0100, Bernhard R. Link wrote:
> * Marcelo E. Magallon <mmagallo@debian.org> [011210 13:46]:
> > that is, allow for '/etc/init.d/myservice start' to work even if the
> > configuration says it shouldn't, e.g., '/etc/init.d/myservice --force
> > start'.
>
> Why should this be introduced into debian?
>
> What is to start is coded within the symlinks. And to force an start you
> just do /etc/init.d/whatever.
There are advantages to having policy separated from the symlinks. For
example, try installing a miniature Debian system within a chroot, when
you don't want any daemon to start because they're all running in the
external system. In fact, starting some of them can cause your system to
become unstable, but you need them installed to satisfy dependencies.
Hacking this is difficult because all the packages will helpfully
install the symlinks and start the service for you, so you need a
separate system which all the packages use to decide on policy.
What this is called, of course, is invoke-rc.d(8) and policy-rc.d(8).
The former already exists, and according to its author the other
necessary changes will happen in woody+1.
--
Colin Watson [cjwatson@flatline.org.uk]
Reply to: