Op 31-10-13 02:50, Theodore Ts'o schreef: > On Wed, Oct 30, 2013 at 06:18:29PM -0700, Russ Allbery wrote: >> I suspect you and I have a root disagreement over the utility of exposing >> some of those degrees of freedom to every init script author, but if you >> have some more specific examples of policy that you wanted to change but >> couldn't, I'd be interested in examples. > > It's not necessarily the init script author who might want the degrees > of freedom, but the local system administrator. > > The most basic is the idea that whether you can control (via shell > scrpit fragments) whether or not a service should start at all, and > what options or environments should be enabled by pasing some file. > The fact that we can put that sort of thing in configuration files > such as /etc/default/*, for example.
This, in my opinion, is one of the worst abominations we currently have in Debian. Whether an init script should run at boot time has no relation whatsoever to whether it should run when the system administrator calls it manually. Yet, with "ENABLE=" variables in /etc/default, this is related, because the initscript will say "I'm disabled, go edit this file if you want to start me", even if you just want to start a daemon just this once manually, for testing. AIUI, both upstart and systemd have configuration options where you can tell the system that this particular service should not start at boot; that will then, however, not affect the result when one manually tries to start the service. I'm not sure that's a very good argument ;-) -- This end should point toward the ground if you want to go to space. If it starts pointing toward space you are having a bad problem and you will not go to space today. -- http://xkcd.com/1133/ -- To UNSUBSCRIBE, email to debian-ctte-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52721ab2.7030...@debian.org
