Re: Bug#727708: tech-ctte: Decide which init system to default to in Debian.
On Wed, Oct 30, 2013 at 10:52:15PM -0700, Russ Allbery wrote:
> >> You can do quite a bit with the hooks that are part of the specification
> >> of both types of files. For example, logic that you may add to control
> >> whether the service should start at all can be implemented by adding a
> >> pre-start stanza to the upstart configuration.
> > ExecStartPre=/bin/false
> > will make the service be considered failed. The ExecStartPre line can
> > of course be an executable that implements more checking or logic.
> Ah, thank you! I got lost in the systemd.* man pages and didn't find the
> systemd.service one somehow (even though it's right there listed first;
I found the systemd man pages, and came across the definition
ExecStartPre, but I didn't make the connection that returning false
would be sufficient to stop the daemon from starting. It was there,
but that's the difference between a reference manual and a
tutorial/cookbook -- a reference manual won't necessarily explain the
implifications of "the unit fails".
The upstart documentation, from my brief examination, seems to be much
more approachable for someone who is starting from ground zero.