<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [bug] weston-launch leaves behind defunct procs when killed, hanging ttys" href="https://bugs.freedesktop.org/show_bug.cgi?id=62910#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [bug] weston-launch leaves behind defunct procs when killed, hanging ttys" href="https://bugs.freedesktop.org/show_bug.cgi?id=62910">bug 62910</a> from <a class="email" href="mailto:krh@bitplanet.net" title="Kristian Høgsberg <krh@bitplanet.net>"> Kristian Høgsberg</a> <pre>Right now weston-launch and weston cooperate to shut down cleanly. Weston catches SIGSEGV and SIGABRT and cleans up as best as it can with help from weston-launch. So killing weston is fine and should work, though SIGKILL can't be caught and doesn't let weston shut down nicely, so that will lock up the system. Killing weston-launch isn't something we've tried to make work well and it will leave weston hanging trying to read from the socket to weston-launch while having the system stuck with keyboard disabled. So in short, don't kill weston-launch, kill weston. weston-launch now returns exit codes to reflect how weston exited: 0 means all is well, 10+signal means weston dies from signal and 128+signal means that weston-launch itself took a signal. In the future, I think we'll move some of the "dangerous stuff" out of weston and into weston-launcher. Things like vt switch and disabling kb and switching the console into graphics mode may be better done in launcher so that no matter how weston dies, weston-launch can always clean it up. When we do that, we'll also teach weston-launch to clean up properly when it itself crashes.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>