Sorry for the spam. Further tracking down the issue. I think I've come to a conclusion of the scenario:
S1.service requires/after D.device and S2.service S1 is activating, thus starts D and S2 S2 starts, which activates D and deactivates D A "can" now start because D has no job running [1], but D is not there anymore. Will try to create a couple of services to reproduce the problem. Best regards, [1] http://lxr.devzen.net/source/xref/systemd/src/core/job.c#429
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
