Re: Feedback needed: How to disable services at startup... and keep them so.
On Tue, Dec 7, 2010 at 1:35 PM, Camaleón <noelamac@gmail.com> wrote:
> On Tue, 07 Dec 2010 10:51:11 -0600, Arthur Machlas wrote:
>
>> On Tue, Dec 7, 2010 at 10:21 AM, Camaleón wrote:
>
> (...)
>
>>> Before I fill a bug report (I think a service that has been manually
>>> disabled should keep its state regardless any further update it can be
>>> applied afterwards), I would like to get some feedback... what do you
>>> think on this matter? I missed something -there is a better way to
>>> handle this or should I write a report?
>>
>> I'd definitely hold off on the bug report. I think you should look at
>> the lsb headers of the network-manager script in /etc/init.d and change
>> them to stop on all levels, start on none, then run "insserv" without
>> any arguments to again disable network-manager. If this isn't a future
>> proof method of disabling it then there is definitley a problem in that
>> packages update maintenance scripts.
>
> Are you suggesting to manually edit the "/etc/init.d/network-manager"
> script header to fit my needs? Correct me if I'm wrong, but I expect this
> file (as any file located here) can be updated at any time and so
> replacing any of the customized values I can have written in there :-?
>
Yes, that is what I am suggesting. And if the upgrade overwrites your
changes, you should file a bug report and ask the maintainer to come
into compliance with Debian Policy:
The /etc/init.d scripts must be treated as configuration files, either
(if they are present in the package, that is, in the .deb file) by
marking them as conffiles, or, (if they do not exist in the .deb) by
managing them correctly in the maintainer scripts (see Configuration
files, Section 10.7). This is important since we want to give the
local system administrator the chance to adapt the scripts to the
local system, e.g., to disable a service without de-installing the
package, or to specify some special command line options when starting
a service, while making sure their changes aren't lost during the next
package upgrade. [1]
AND
Configuration file handling must conform to the following behavior:
- local changes must be preserved during a package upgrade, and
- configuration files must be preserved when the package is removed,
and only deleted when the package is purged. [2]
Best,
AM
[1] http://www.debian.org/doc/debian-policy/ch-opersys.html#s-sysvinit
[2] http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files
> I can try it though, just want to be sure this is not going to cause any
> problem in the future :-)
>
> Oh, and thanks both, Mike and you, for replying.
>
> Greetings,
>
> --
> Camaleón
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: [🔎] pan.2010.12.07.19.35.56@gmail.com">http://lists.debian.org/[🔎] pan.2010.12.07.19.35.56@gmail.com
>
>
Reply to: