Problem when trying to use -nolock Option
Thu Jul 1 14:45:00 GMT 2010
On 01/07/2010 06:53, Mathias Friesenbichler wrote:
> Thanks for the reply. But you didnât get my problem.
> We are several users running X servers over several computers, but starting the X from the same Installation on the network.
I see. You didn't mention this before.
I don't think that's a supported way of running cygwin.
Things would probably work better if you set the mount table for each computer
so it had /tmp mounted on a local disk, rather than having them all share one.
> So the local Computer doesnât know anything about the other users and therefore we have written a program that manages this problem for us. This program gives each user a unique display number.
> The problem now is that if I use the â-nolockâ option it does the same as if I donât use it. It also creates those lockfiles.
> So what can I do to fix this?
The "/tmp/.X11-unix/Xn" files are not lock files. They are unix domain sockets.
You could avoid them being created by using '-nolisten unix', which probably
avoids this specific problem.
Volunteer Cygwin/X X Server maintainer
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
More information about the Cygwin-xfree