<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - when a unit file is removed, systemd abandons running processes" href="https://bugs.freedesktop.org/show_bug.cgi?id=65973#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - when a unit file is removed, systemd abandons running processes" href="https://bugs.freedesktop.org/show_bug.cgi?id=65973">bug 65973</a> from <a class="email" href="mailto:lennart@poettering.net" title="Lennart Poettering <lennart@poettering.net>"> Lennart Poettering</a> <pre>So, if libvirt doesn't move qemu away, then this indeed looks like a bug in systemd. When you remove the service description file and the service is still running at that time, and you reload systemd, then systemd should show the thing as failed to load, but should still show all its running processes, and it should allow shutting the service down (which would use the default shutting down logic of SIGTERM+SIGKILL given that no other config is available). It wouldn't allow restarting, reloading or starting it, only stopping it, since that is kinda necessary, and that's the only thing we actually can do without service description file. Zbigniew's pastes suggest that for some reason systemd completely loses track of the processes when it is reloaded. And that definitely shouldn't happen. And I am sure this did work once upon a time, because I remember hacking this up and testing it.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>