On 04/04/2012 03:29 PM, Chase Douglas wrote:
This option specifies a file descriptor in the launching process. X
will scan for an available display number and write that number back to
the launching process, at the same time as SIGUSR1 generation. This
means display managers don't need to
On 04/05/2012 07:46 AM, Adam Jackson wrote:
On Thu, 2012-04-05 at 09:39 +0100, Daniel Stone wrote:
Hi,
On 5 April 2012 06:19, Chase Douglas chase.doug...@canonical.com wrote:
On 04/04/2012 07:18 PM, Alan Coopersmith wrote:
Thanks. (I do note that you removed the \n from the display and
Hi,
On 5 April 2012 06:19, Chase Douglas chase.doug...@canonical.com wrote:
On 04/04/2012 07:18 PM, Alan Coopersmith wrote:
Thanks. (I do note that you removed the \n from the display and
didn't add it to the write of the display to the fd - I don't know
if that matters or not, so figured
On Thu, 2012-04-05 at 09:39 +0100, Daniel Stone wrote:
Hi,
On 5 April 2012 06:19, Chase Douglas chase.doug...@canonical.com wrote:
On 04/04/2012 07:18 PM, Alan Coopersmith wrote:
Thanks. (I do note that you removed the \n from the display and
didn't add it to the write of the display
This option specifies a file descriptor in the launching process. X
will scan for an available display number and write that number back to
the launching process, at the same time as SIGUSR1 generation. This
means display managers don't need to guess at available display numbers.
As a
On 04/ 4/12 03:29 PM, Chase Douglas wrote:
This option specifies a file descriptor in the launching process. X
will scan for an available display number and write that number back to
the launching process, at the same time as SIGUSR1 generation. This
means display managers don't need to
On 04/04/2012 07:18 PM, Alan Coopersmith wrote:
On 04/ 4/12 03:29 PM, Chase Douglas wrote:
This option specifies a file descriptor in the launching process. X
will scan for an available display number and write that number back to
the launching process, at the same time as SIGUSR1 generation.
