On Tue, 06.01.15 16:33, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
> > Isn't that just bad behavior? Sending a RELOADING=1 notification after > > a reload is initiated? I guess if both service_enter_reload() and > > service_enter_reload_by_notify() are called it is justified to > > propagate two reloads. Before testing it might be nice to know what we > > want :-). > > Hm. Looking at the code, sending periodic RELOADING=1 notifications > can be used to sidestep the timeouts. This does not look OK, but maybe > I'm misreading the code. I think you are reading the code right. Not sure though whether that should be considered a bug though... Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
