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

[Camaleón <noelamac@gmail.com>]

On Thu, 09 Dec 2010 07:07:11 -0500, Tom H wrote:

> On Thu, Dec 9, 2010 at 6:11 AM, Camaleón wrote:

(...)

>> The warning can be ignored but the service levels are not touched and
>> it does not work as expected (meaning, the service is not disabled at
>> all).
> 
> It was silly of me to say that the warning can be ignored given that my
> own testing showed that nothing was done...

The warning can be ignored (see my last "solved" marked message):

http://lists.debian.org/debian-user/2010/12/msg00505.html

The warning is still there but it works.

>>> Furthermore, how does insserv deal with the scripts if you assign S20
>>> to network-manager and it depends on a service that insserv has
>>> numbered S21?
>>
>> It can be tweaked or so it says man page :-)
> 
> Which man page? Since you're using update-rc.d, of course you can assign
> a start number higher than 21 with update-rc.d if a service depends on a
> service that insserv has numbered 21. My point was more "how do you know
> the highest start number that insserv has assigned to a service that
> service that you're editing depends upon?"

You can look at the /etc/init.d/* folder and in the scripts headers.
 
>>> If you're using Squeeze/Sid and therefore have an insserv-controlled
>>> boot-process, why not use an insserv solution?
>>>
>>> There's more typing to be done but it works.
>>
>> Simple, because it wasn't the advertized method for doing it.
> 
> man insserv

I can't see there how to disable a service nor examples on how to achieve 
it  :-?

>>> I've just tried "update-rc.d -f remove nfs-kernel-server; update-rc.d
>>> nfs-kernel server stop 2 3 4 5 ." and rebooted to find that
>>> nfs-kernel-server is still running.
>>
>> Yep. But you missed the level number.
> 
> The level number isn't needed.

The example command in man page makes use of it, but it neither works :-/

Greetings,

-- 
Camaleón