On Fri, 2017-01-06 at 16:05 -0700, stan wrote: > I think systemd has to have some sort of task ordering, or it couldn't > function, since there *are* ordering dependencies during boot. They > are probably just fuzzy, though. And there are things like the wait > on network task to try to protect against out of order start. I doubt that the dependencies are "fuzzy". What would that even mean? AFAIK they define a partial order and each process just executes as soon as it can. That's why the physical order can vary. You want a way for the partial ordering to be converted to a fixed total ordering under control of some option, but I don't know if that's possible without rewriting a lot of systemd rules. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
