[PATCH] Introduce weston-launch

Tiago Vignatti tiago.vignatti at linux.intel.com
Wed Feb 1 07:14:23 PST 2012

On 02/01/2012 04:37 PM, Benjamin Franzke wrote:
> You mean to start weston and weston-launch (the permission part) seperately?
> We could do that, but thats of course not that handy, and would
> produce two problems:
>   - The tty would need to be chowned to the user
>   - The control socket couldn't be passed through fork.
>     (a unix socket wouldnt suffice since other applications could use
> that as well)
> So that would really be a debugging-only solution.
> Instead we can just keep the possibility to start weston without
> weston-launch, as its done now.

I meant that I want still open weston directly without a glued daemon 
coming behind. And yes, for debugging only, so it's okay to start as 
root for instance. I thought the we way you were suggesting, we wouldn't 
be able to start weston without the daemon.

> And for debugging weston with weston-launch there is the sleep option,
> so you can start weston-launch,
> and attach to weston using gdb --pid.

IMHO we don't need this sleep at all, but if you find useful at least 
document properly (in -help output and in the code) why is needed for.


More information about the wayland-devel mailing list