insserv -r is no option, because on the next update the default run level symlinks are reinstalled again. Thats even worse than creating a private overrides file for insserv. Not to mention that insserv nags about some "non-default" run level symlinks all the time.
I completely agree that duplicate methods to configure run level scripts should be avoided. But it should also be clear that the config file and the item to config (eg. when to run the script) should be kept separate from each other. Maybe a look at other Unixes helps? SunOS 5.x (just as an example) provides a tool "svcadm" to manage which services are started at boot time. On SunOS 5.x there is no need to create a new config file with a weird syntax in an "overrides" directory to make sure that a hard- wired configuration in the startup script gets ignored. Regards Harri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
