On Fri, 24.04.15 15:52, Lennart Poettering (lenn...@poettering.net) wrote: > On Wed, 25.02.15 21:40, Ivan Shapovalov (intelfx...@gmail.com) wrote: > > Ivan, > > > Because the order of coldplugging is not defined, we can reference a > > not-yet-coldplugged unit and read its state while it has not yet been > > set to a meaningful value. > > > > This way, already active units may get started again. > > > We fix this by deferring such actions until all units have been at least > > somehow coldplugged. > > > > Fixes https://bugs.freedesktop.org/show_bug.cgi?id=88401 > > Hmm, so firstly, in this case, do those two alsa services > have RemainAfterExit=yes set? I mean, if they have not, they really > should. I they have, then queuing jobs for them a second time is not > really an issue, because the services are already running they will be > eaten up eventually.
Oh, is there a simple reproducer for the issue btw? Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
