https://bugs.freedesktop.org/show_bug.cgi?id=60926
--- Comment #4 from U. Artie Eoff <[email protected]> --- (In reply to comment #3) > 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? -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Wayland-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-bugs
