[Pkg-sysvinit-devel] policy-rc.d doesn't work?

Bob Proulx bob at proulx.com
Mon Apr 22 16:24:36 UTC 2013


Hi Petter,

Thanks for the information.

Petter Reinholdtsen wrote:
> Bob Proulx wrote:
> > Then according to the docs no daemons should be started.  But when I
> > reboot all daemons are running normally.  In spite of the policy-rc.d
> > script the init scripts were all still run.
> 
> policy-rc.d is invoked by update-rc.d when a package is installed and
> removed, and not by the individual init.d scripts when the machine or
> service is started.

So just to be clear policy-rc.d doesn't in any way set the policy of
daemons being started or stopped through the rc?.d scripts?

I am flabbergasted!  There is this quite complete infrastructure that
has been developed but not implemented?  Wow.  It definitely suckered
me in like an elaborate April Fool's prank.  I think I will go harvest
some spaghetti from trees now.

> > What am I missing?
> 
> Clear documentation, I suspect. :)

I am befuddled.  Why was so much effort put into creating such a
detailed infrastructure that doesn't do what it so obviously seems
like it should be doing?  I will read through Bug#76868 in detail and
see if there are clues there.  To be honest I had only very briefly
skimmed it previously.

  INIT SCRIPT POLICY
       invoke-rc.d introduces the concept of a policy layer which is
       used to verify if an init script should be run or not, or if
       something else should be done instead.

Hmm...  Should it have been called policy-init.d instead?  :-/

Thanks,
Bob
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-sysvinit-devel/attachments/20130422/afaafe51/attachment.pgp>


More information about the Pkg-sysvinit-devel mailing list