On 01/07/2010 06:53, Mathias Friesenbichler wrote:
Hi,
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.
--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
