Comment 23 for bug 94065

Indeed, all of those things work.

The reason for the ".conf" suffix is because editors frequently write
temporary working files into the same directory as the original file,
they also write backup files, and package managers frequently write
"old or new" files into the directory as well.

You end up with a huge amount of filter code to exclude "FILE.bak"
"FILE~" "#FILE#' "FILE.dpkg-new" "FILE.dpkg-old" "FILE.rpm-tmp" etc.
And every time a new editor or package manager gets invented, you have
to run to catch up.

Thus it was decided amongst the group of developers working on
plumbing-layer tools to use extensions.

Scott

On Thu, Dec 30, 2010 at 5:20 PM, paul fox
<email address hidden> wrote:
>
> "expected to uninstall?"  says who?  as the original submitter of this bug, let me be the one to point out this phrase from the description:  "this might be to temporarily disable a serial line getty, or whatever."  that doesn't sound like a reason to uninstall to me.
>
> in any case, i think this bug has been fixed for some time:  you can
> already comment out the "start" line, or, apparently, add a "manual"
> line.  and if the (dumb, in my opinion) requirement for using a .conf
> suffix (why are we trying to reinvent DOS?) is fully implemented, then
> renaming the file to "myservice.disabled" should accomplish the same
> thing.
>
> --
> 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.
>
>
>