public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk> To: cygwin-xfree@cygwin.com Cc: Hiasi1@gmx.at Subject: Re: Problem when trying to use -nolock Option Date: Thu, 01 Jul 2010 14:45:00 -0000 [thread overview] Message-ID: <4C2CAA0A.7080706@dronecode.org.uk> (raw) In-Reply-To: <20100701055355.190770@gmx.net> 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/
next prev parent reply other threads:[~2010-07-01 14:45 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <899957031274A04FB53CA5077F5C1367033D7A6D6F@MAILSTORE.LAG.AT> 2010-07-01 5:54 ` Mathias Friesenbichler 2010-07-01 14:45 ` Jon TURNEY [this message] 2010-06-29 16:13 Mathias Friesenbichler 2010-06-30 18:03 ` Jon TURNEY -- strict thread matches above, loose matches on Subject: below -- 2010-06-17 6:24 Mathias Friesenbichler
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=4C2CAA0A.7080706@dronecode.org.uk \ --to=jon.turney@dronecode.org.uk \ --cc=Hiasi1@gmx.at \ --cc=cygwin-xfree@cygwin.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).