<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><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#c2">Comment # 2</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 <span class="vcard"><a class="email" href="mailto:joe.konno@linux.intel.com" title="Joe Konno <joe.konno@linux.intel.com>"> <span class="fn">Joe Konno</span></a>
</span></b>
<pre>Appreciate the insights. Thanks, krh!
(In reply to <a href="show_bug.cgi?id=62910#c1">comment #1</a>)
<span class="quote">> 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.</span ></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>