[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#661496: marked as done (multiple, annoyingly different ways to disable an init script)



Your message dated Mon, 9 Dec 2013 15:27:11 +0100
with message-id <201312091527.12534.holger@layer-acht.org>
and subject line thats the way these init scripts are, use something else if you care about this
has caused the Debian Bug report #601455,
regarding multiple, annoyingly different ways to disable an init script
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
601455: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601455
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: general
Severity: minor
Tags: patch

When I try to stop a daemon after I disabled it in /etc/default/foo, I get an error-message that I can not stop it, because it is disabled.

Shouldn't I be able to stop it even if I disabled it first?

This happens if you disabled a daemon but didn't restart after that.

In my case it's MPD, I even tried it with icecast2, but I think this applies to more than these packages.

-----------
user@sys:~$ sudo /etc/init.d/mpd stop
Not stopping MPD: disabled by /etc/default/mpd. failed!

user@sys:~$ sudo /etc/init.d/icecast2 stop
icecast2 daemon disabled - read /etc/default/icecast2.
-----------

E.g. in /etc/init.d/icecast2 I changed
- if [ "$ENABLE" != "true" ]; then
to
+ if [ "$ENABLE" != "true" ] && [ "$1" != "stop" ]; then

Best regards,
Mathias Kub

-- System Information:
Debian Release: lenny



--- End Message ---
--- Begin Message ---
Hi,

I've decided to close this bug, as this "mis-feature" / bug is actually a main 
characteristic of system V init scripts: they can be+do anything, including 
showing the behaviour which led to this bug report.

If you don't like this, use a modern init system.


cheers,
	Holger

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply to: