On 16.03.2012 22:05, Michael Biebl wrote: > If invoke-rc.d intercepts and redirects the request to upstart (or > systemd), should update-rc.d do the same? > > Say you run "update-rc.d <service> disable", should this disable only > the sysv init script, both, or only the upstart/systemd service?
The reason, why I brought this up, is this: Say you run upstart/systemd and a you have a package which provides a sysv init script foo, which you have disabled. On upgrades, invoke-rc.d will respect and not run the service. In version X, your packages starts shipping a upstart job file. In this case invoke-rc.d will happily run the upstart job. Do we require maintainers to preserve the on/off state of the service, if they start shipping a native upstart/systemd job? What would be the interface for that? Would this be a one-time migration or done on each package upgrade? Do we "somehow" ensure the on/off state of the service is kept consistent between the different init systems, so it doesn't matter when I switch from sysvinit to upstart (or back again)? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
