Because, believe it or not, it's not a very common use case - in the Debian and Ubuntu world, you're generally expected to uninstall services you don't need.
Also the Dpkg package manager *honours* deletes as a conffile change, so if you simply delete the job (or change its extension) it won't come back after an upgrade. But as I said in my last comment, there is now an easy way to mark a job as manual - and in the next release, this won't even require editing the .conf file Scott On Thu, Dec 30, 2010 at 7:32 AM, MestreLion <launch...@rodrigosilva.com> wrote: > "slightly embarassinng"? Youre being very kind... > > Its a complete shame for Upstart not to have ANY means to disable > services at startup. > > More incredibly is that Ubuntu (and even Debian) is now migrating to it. > > So now we are back to the old days of manually editing scripts? Hows > that ANY improvement? Not everyday a tool achieves being bad for both > desktop end users AND server sysadmins... > > -- > You received this bug notification because you are a member of Upstart > Developers, which is subscribed to upstart . > https://bugs.launchpad.net/bugs/94065 > > Title: > init: add non-destructive means to disable a job > > Status in Upstart: > Triaged > Status in “upstart” package in Ubuntu: > Invalid > > Bug description: > I need the ability to disable an event.d entry without removing the entry > completely. this is the equivalent of commenting a line in /etc/inittab. > this might be to temporarily disable a serial line getty, or whatever. > > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/94065 Title: init: add non-destructive means to disable a job -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
