> Date: Mon, 9 Dec 2013 15:27:11 +0100 > From: Holger Levsen <holger@layer-acht.org> > To: 601455-done@bugs.debian.org > Subject: thats the way these init scripts are, use something else if you care about this > > 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. That doesn't make it an unreasonable expectation. I've seen the same issue as well, and it always annoyed me. Why shouldn't we write this in policy? "It must be possible to stop a service with its init script, even if the package is disabled by its configuration files." Your argument is "a shell script can do this, therefore it is not a bug if it does", which is nonsense. A shell script can also remove all files in /bin, and it definitely is a critical bug if it does. > If you don't like this, use a modern init system. Yes, because that's non-controversial and all. I'll wait until the war is over to switch to whoever won. That doesn't mean any actual buggy behavior on my system is to be ignored as "use a modern init system". I am running the newest version of the packages in Debian; this is a configuration we should support. When Debian no longer supports sysv init, a reply like this is acceptable. Currently it is not. Note that I would consider it acceptable to not fix these bugs until a decision about init systems has been made. But they are still real bugs, even if we decide not to fix them. Thanks, Bas
Attachment:
signature.asc
Description: Digital signature