<div dir="ltr">Of course I mean WAYLAND_DISPLAY, not WAYLAND_SOCKET. Whoops.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, May 7, 2014 at 9:05 AM, Jasper St. Pierre <span dir="ltr"><<a href="mailto:jstpierre@mecheye.net" target="_blank">jstpierre@mecheye.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This patch series implements a better fallback than a hardcoded<br>
"wayland-0" when a server socket has already been taken. This way,<br>
the code for searching for an appropriate socket is shared between<br>
all compositors.<br>
<br>
The option to open an explicit socket still exists, if the client<br>
specifies it.<br>
<br>
Jasper St. Pierre (3):<br>
server: Create the socket FD after taking the lock<br>
server: Split out code to open sockets for a specific name<br>
server: Find an open wayland-* socket by default<br>
<br>
src/wayland-server.c | 77 ++++++++++++++++++++++++++++++++++++----------------<br>
1 file changed, 54 insertions(+), 23 deletions(-)<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
1.9.0<br>
<br>
</font></span></blockquote></div><br><br clear="all"><br>-- <br> Jasper<br>
</div>