Tollef Fog Heen wrote: > > Russ Allbery wrote: > > > Bob Proulx writes: > > > > Maybe I am missing a better alternative? > > > > > > update-rc.d <service> disable > > > > No. That is too late. By the time you are disabling something it has > > already been installed and started in postinst scripts. Using > > policy-rc.d is the only way to prevent unknown anythings from being > > enabled before installing. That installation may be due to a > > dependency. Think dnsmasq. Also update-rc.d only configures the boot > > time configuration. It doesn't affect things until you reboot. It > > doesn't affect postinst scripts. Using update-rc.d is not a solution. > > Have your policy-rc.d call update-rc.d <service> disable too. Hmm... That is twisted. But I kind'a like it! :-) If nothing else if I added logging to policy-rc.d then ran through a full system install and provisioning then I could get an initial list of the packages and daemons that are trying to be started. Bob
Attachment:
signature.asc
Description: Digital signature