[systemd-devel] contingent After

[Michal Schmidt]

On 11/05/2011 06:09 PM, Michael D. Berger wrote:
> Thanks to the help provided by members of the list,
> myDaemon is now functioning correctly under systemd.
>
> Now for myUpperDaemon:
>
> IF myDaemon is enabled; then
>     myUpperDaemon must start after myDaemon
> ELSE
>     myUpperDaemon must start anyway
> ENDIF

This exactly what "After=myDaemon.service" is for. Realize that in 
systemd you can express requirement dependencies (Wants, Requires, ...) 
completely independently of ordering dependencies (Before, After).
The situation you described is a case of an ordering dependency, without 
a requirement dependency.

Michal