This is a second call for objections to #156161 as restated in my recent posting to this list. http://marc.theaimsgroup.com/?l=debian-devel&m=106150585805521&w=2
To recap, the idea is that invoke-rc.d be modified such that it _not_change_ the state of a service (i.e., neither start it nor stop it) on entering a runlevel if there is neither a start link nor a stop link for the service in that runlevel. This would allow a service to be removed from the control of the runlevel system by deleting its rc symlinks; the service would then be entirely under manual control -- the admin would start and stop the service by running the initscript. This would be consistent with invoke-rc.d's documentation: invoke-rc.d itself will [...] block any tries to start an init script in a runlevel it is not configured to be started at. Currently one can delete the rc symlinks for a service but invoke-rc.d interprets the absence of the stop symlink as permission to start the service. This can't be called a bug because the invoke-rc.d(8) passage above is ambiguous. -- Thomas Hood
