On Mon, 21 Jun 2004, martin f krafft wrote: > The recommended way to disable a service, or to move its > initialisation priority is update-rc.d. However, when the package is
update-rc.d is for THE PACKAGING SYSTEM. It is not meant as an admin tool. It could be made smarter, like dpkg-divert, and then it would be usable as an admin tool. But right now, it isn't. > upgraded, it is likely that the choice I made for update-rc.d will > be overwritten. Since update-rc.d does not have a similar backend Not really. In fact, not at all. As long as one link remains, update-rc.d won't change anything. Now, if you want to *disable* the service, as in *keep it stopped*, then change all links to "K" links. If you want to *leave the service alone*, policy-rc.d is the only way, otherwise package upgrades will cause the service to be restarted right now (but if you left one stop link, e.g. for runlevel 0, in place, they will not screw around with your runlevel setup). > or `exit 0` at the top of the init script? (ugh!) That one certainly works, even with buggy packages, or those which haven't switched to invoke-rc.d yet. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
