How about adding an "--order" option to systemctl? With this option, systemctl will sort those units by ordering dependencies before submitting them. Although I personally wanted this to be the default behavior, I can understand comparability matters.
John Lin Reindl Harald <h.rei...@thelounge.net> 於 2018年1月12日 週五 上午4:57寫道： > > Am 11.01.2018 um 20:27 schrieb Andrei Borzenkov: > > 11.01.2018 21:56, Reindl Harald пишет: > >> > >> it complete unexpected nonsense when i have two services which have a > >> clear start ordering > > > > "services start ordering" is fundamental misconception. Ordering exists > > between jobs, not units. Unfortunately, systemd documentation does very > > little to explain it > > come on - nobody cares about this bullshit bingo about what are jobs, > units and services > > "systemctl restart a.service b.service" are two jobs when you want it to > call that way witch a implicit ordering defined with After/Before when > you want it to call job > > just because i give you 2 tasks at the same time you are not supposed to > do them at the same time when you look at them and see a benefit for > both in doing it in a specific order > > *please* forget the bullshit bingo > > when i have to look into avery unit if it contains After/Before to fire > up the restarts ina correct order by hand something is broken - it's > really that simple > _______________________________________________ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd-devel >
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
