<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Weston should exit when run on KMS without weston-launch"
href="https://bugs.freedesktop.org/show_bug.cgi?id=60926#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Weston should exit when run on KMS without weston-launch"
href="https://bugs.freedesktop.org/show_bug.cgi?id=60926">bug 60926</a>
from <span class="vcard"><a class="email" href="mailto:krh@bitplanet.net" title="Kristian Høgsberg <krh@bitplanet.net>"> <span class="fn">Kristian Høgsberg</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=60926#c4">comment #4</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=60926#c3">comment #3</a>)
> > weston-launch is the only supported way to run weston on KMS. weston-launch
> > isolates the few things requiring root-priviledges in a tiny process with no
> > unsafe dependencies for easy auditing, letting weston run as a regular user.
> > Running weston on kms can only work if it is run as root, which is not a
> > scenario we support.
>
> Yes, we have weston permissions as suid root and run it that way. IIRC, the
> reason we initially avoided weston-launch was because it always return an
> exitcode of 0 regardless of how weston exited. This was bad for detecting
> if weston crashed during an automated test. Curiously, I just tried running
> weston-launch again and now I always get a "Hangup" message with exitcode
> 129 regardless of how I kill weston (i.e. SIGTERM, SIGKILL, SIGABRT,
> SIGSEGV). This makes it even more difficult (from a testing perspective) to
> detect "weston as the cause" for test failures. Is there any technical
> reason why weston-launch couldn't exit with weston's exitcode?</span >
That's a good point - we should do that.</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>