[Nathan Scott] > For PCP we have several daemons in the one package (as you see above > in that ls output) and depending on the deployment, maybe some > should be enabled, and maybe some not ... its not necessarily a bad > thing to leave that choice up to the administrator, in the end, for > PCP.
Well, the package used to enable them all, and I provided headers assuming that the old behaviour should be kept. > Is there any downside (other than not auto-starting in boot) to not > having Default run levels set in the script? Is it required / > policy to do so? I couldn't find docs that suggest that is/isn't > the case anywhere. Yes, it make it hard to enable the service, as the headers need to be overridden or the init.d scripts edited before update-rc.d will enable the scripts. If you do not want to enable the service at boot after initial installation, you should change the postinst to not call update-rc.d instead of removing the runlevels from the default-* headers. I do not have any references available, but in Debian services are normally expected to work out of the box after installation. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
