[systemd-bugs] [Bug 68878] systemd does not execute multiple ExecStart after a daemon-reload

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Sep 13 04:10:05 PDT 2013


https://bugs.freedesktop.org/show_bug.cgi?id=68878

--- Comment #2 from Harald Hoyer <harald at redhat.com> ---
(In reply to comment #1)
> The problem here is that we have trouble recognizing the same ExecStart=
> lines before and after we did the reload, hence we currently don't try at
> all.
> 
> i.e. let's say you have three ExecStart= lines:
> 
> ExecStart=/bin/foo
> ExecStart=/bin/bar
> ExecStart=/bin/waldo
> 
> Let's say you are now executing /bin/bar. And now you reload the daemon, but
> the /bin/bar one was removed, what do you do now, at which point do you
> continue? And what happens if it's /bin/foo you remove too? And what happens
> when you delete all three and replace them with ExecStart=/bin/huhu?
> 
> We should probably do something about this and try to come up with a scheme
> that at least most of the time manages to continue at some sane point. But I
> am not sure what the best scheme here would be? Ideas?

Well, maybe delay the daemon-reload until a point of time, where we can safely
do that.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20130913/8d7e6043/attachment.html>


More information about the systemd-bugs mailing list