Re: Feedback needed: How to disable services at startup... and keep them so.

[Paul Lane <kc9eye@gmail.com>]

On Tue, Dec 7, 2010 at 10:21 AM, Camaleón <noelamac@gmail.com> wrote:
> Hello,
>
> A month ago, I disabled Network Manager service in my Squeeze system so
> it doesn't run on start up. I wanted to keep NM installed (just in case)
> but preferred to use the old "ifup" network setup method.
>
> So I issued "update-rc.d network-manager remove" and also disabled gnome
> NM applet from being started. So far so good, no more NM running at
> booting.
> I missed something -there is a better way to handle
> this or should I write a report?
>
> Greetings,
>
> --
> Camaleón
AFAIK, the method to disable a boot time service is to change the name
of its symlink in the appropriate runlevel (normally 2, for debian)
folder. I'm not sure what the name of the NM script is as I did this
many moons ago. But, if you look in /etc/rc2.d/, you will find a
README that explains it all. Reprinted here for clarity:

"The scripts in this directory are executed each time the system enters
this runlevel.

The scripts are all symbolic links whose targets are located in
/etc/init.d/ .

To disable a service in this runlevel, rename its script in this directory
so that the new name begins with a 'K' and a two-digit number, where the
number is the difference between the two-digit number following the 'S'
in its current name, and 100.  To re-enable the service, rename the script
back to its original name beginning with 'S'.

For a more information see /etc/init.d/README."

-- 
Paul Lane
KC9EYE
-----------------------------------------------------------------------------
""Water which is too pure has no fish."
----------------------------------------------------------------------------