Bug#727708: upstart and upgrading from sysvinit scripts

[Russ Allbery <rra@debian.org>]

Tollef Fog Heen <tfheen@err.no> writes:

> ]] Russ Allbery 

>> It would, however, be nice if this were more clearly stated, since the
>> guidance to the author of the unit file about what dependencies one should
>> or should not explicitly add is a bit sparse.  In particular, I wonder if
>> there is an implicit After= dependency in a service unit on a socket unit
>> of the same name (which would make sense given how Sockets= works), or if
>> that's something that one should explicitly add.

> http://www.freedesktop.org/software/systemd/man/bootup.html has some
> graphs.  In addition, as long as your service is not doing anything in
> the early boot, DefaultDependencies will be true and you'll have an
> After=basic.target in your service.

This by itself doesn't fully replace the implicit dependency.  It ensures
ordering is correct for boot, but not that ordering is correct when
starting deactivated services, where the service startup is not happening
in the context of target processing.  (Unless target processing happens in
more places than I think it does.)

It sounds, from Uoti's investigations, that the code also directly adds an
implicit dependency, which would ensure correct behavior in those cases as
well.

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>