On Mon, 25.08.14 22:23, Ivan Shapovalov (intelfx...@gmail.com) wrote: > > So, I am pretty sure we don#t want an explicit After= order here between > > dbus and systemd-resume@.service... > > > > Hmm, but yuck, I don't see a nice way to fix this for good. Grrr. > > > > I'd probably just merge this as is, and let people who are crazy enough > > to run sysuers or hwdb-update in the initrd, to figure this out. Let's > > just wait until this pops up... > > > > Lennart > > So, do you want me to leave "After=systemd-udevd.service" or remove it? > (An ordering cycle or a waiting timeout?)
Remove it. There's no improvement if you have it, and we don't do it in other cases that are remotely similar to this: services depend on the devices they manage, but never on the device manager itself. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
