2008/11/7 Michael Biebl <[EMAIL PROTECTED]>: > 2008/11/7 Michael Biebl <[EMAIL PROTECTED]>: >> 2008/11/7 Scott James Remnant <[EMAIL PROTECTED]>: >>> On Fri, 2008-11-07 at 15:47 +0100, Michael Biebl wrote: >>> >>>> 2008/11/7 Scott James Remnant <[EMAIL PROTECTED]>: >>>> > On Fri, 2008-11-07 at 14:06 +0100, Michael Biebl wrote: >>>> > >>>> >> 2008/11/7 Scott James Remnant <[EMAIL PROTECTED]>: >>>> >> > In the 0.10 design, this is supported by adding a stanza like >>>> >> > "manual" or "disabled" to the job - or removing one like "auto" >>>> >> > (not yet decided) >>>> >> >>>> >> Where is this information stored? In the job file itself? >>>> >> This imho would be a disadvantage to an external state/profile file, >>>> >> as on package upgrades (at least on Debian and I guess rpm-based >>>> >> distros too), you'd get prompts from the package management system. >>>> >> >>>> > Isn't that correct though? >>>> > >>>> > You'd want the prompt, you disabled a job that has changed. >>>> >>>> Not really. I want the package management system to update the job >>>> file and keep the service disabled, without a dpkg prompt. >>>> >>> Let's take a different example. >>> >>> You as the sysadmin change the conditions under which the service may be >>> running; this is also defined in the job as a "while" clause. >>> >>> On upgrade, the job has changed to have a new condition. >>> >>> Should you get a dpkg prompt there? >>> >> >> Yes, but that is imho a different case. >> What I (and I guess others too) would like, is a simple mechanism to >> enable/disable a job (or switch between "manual" and "automatic" mode, >> if you prefer this term). Something like the symlinks in /etc/rc?.d/ >> I still want to be able to manually run >> start apache >> but e.g. I don't want to have apache started automatically on boot as >> soon as its preconditions are met. > > As a use-case: > > On my laptop I have stuff like mysql-server and apache installed, as I > need them sometimes to develop and test stuff, but I don't need them > running all the time and started automatically on boot. > With sysv, I've removed the S?? symlinks in /etc/rc?.d/ (well, > renamed them to K??) and manually start the services via > /etc/init.d/apache2 when I need them.
Another use case are distros, which don't enable services like apache2 by default, but expect the admin to first check (and modify) the configuration. I guess what I want is something like Solaris' SMF functionality of enabling and disabling services [1] Cheers, Michael [1] http://www.sun.com/bigadmin/content/selfheal/smf-quickstart.jsp -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- upstart-devel mailing list upstart-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel