On Tue, Sep 7, 2010 at 9:46 AM, Paul Smith <p...@mad-scientist.net> wrote: > On Tue, 2010-09-07 at 11:28 +0100, Matthew Paul Thomas wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Paul Smith wrote on 04/09/10 20:46: >> > >> > Esp. how it interacts with Ubuntu/Debian packaging. >> >... >> > So far my Google/etc. searching for admin-level details of upstart >> > hasn't netted me very much. >> >... >> >> Have you found <http://upstart.ubuntu.com/wiki/>? > > Yes, thanks for that. Most pages there are specifications for future > improvements. > > The documentation about today's implementation doesn't give any hints > about how a service can be disabled, a la update-rc.d disable. > > All I can find is the description of the init file.
I don't know if there is an 'official' way to disable a job, but the two ways I have used in the past are: 1) Rename it so that it doesn't end with .conf. Upstart only watches .conf files, so renaming it to .conf.disabled will kill it. 2) Add an unused event (like 'never') to the 'start on' field. As long as nothing emits the 'never' event, then the job will never start. 1 seems more robust in that 2 can still be started by upstart accidentally if something emits an event that it shouldn't. However, I believe 2 plays more nicely with dpkg and how it manages configuration files (upstart files are listed as debian conf files). If you're still looking for a better answer, try asking on https://lists.ubuntu.com/mailman/listinfo/upstart-devel Evan -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
