On Fri, 15.08.14 15:04, Roger Qiu (roger....@polycademy.com) wrote: > > Hello Lennart, > > Thanks for answering. > > Is there any way to enforce ordering to make this error not occur?
You could order systemd-logind.service After= dbus.service. That way dbus is started first, and logind second. And since the top order is the reversed start order, this would result in logind being stopped first and dbus second. But honestly, I don't really like this, we should no add unnecessary ordering here... > Or what's the best way to hide that warning? We should probably just patch it out... > Or when is the ETA for kdbus? Well, "when it's ready"... Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
