> It certainly appears similarly, but the dependency and ordering primitives are interpreted much more loosely like tags than they are like absolute requirements.
Ah. That would be the "subtlety" that I was missing. Thanks! :)
As an aside: how terrible it is to provide an interface that makes it look it gives you ordering guarantees when -in actuality- it gives you no such thing! :(
Re:Systemd v227
by vezzy-fnord on Thursday October 08, 2015 @05:33PM
(#10356454)
Well, in fairness, the developers are honest about it. But they perhaps do not make it as obvious they should, and a lot of people are fooled (I'd cynically argue to the benefit of the systemd developers).
Simplifying things, your unit file actually becomes a Unit object which queues a job (which is itself a Unit) which is scheduled and checked for consistency in a transaction, which encapsulates a service (itself a Unit and one that controls jobs). The final graph of dependency information largely does not reflect what you configured.