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: Wed, 30 Jun 2010 18:03:00 -0000 [thread overview] Message-ID: <4C2B86E4.4040207@dronecode.org.uk> (raw) In-Reply-To: <20100629161332.193930@gmx.net> On 29/06/2010 17:13, Mathias Friesenbichler wrote: > Hi, > > I posted this Problem 2 Weeks ago and no one answered yet. > > Is there anyone who can help me? Yourself, first of all. Try reading the 'Xserver' man page. > Thanks, > Mathias > > -------- Original-Nachricht -------- > Datum: Thu, 17 Jun 2010 08:24:03 +0200 > Von: "Mathias Friesenbichler"<Hiasi1@gmx.at> > An: cygwin-xfree@cygwin.com > Betreff: Problem when trying to use -nolock Option > > Hi, > > My CygwinX is installed on a server. > Several users are accessing this installation and therefore i want to use the "-nolock" option. No. If several users are running X servers on the same computer at the same time, they need to each use a unique display number. '-nolock' is only useful if /tmp resides on a FAT filesystem, which doesn't support the semantics needed by lockfiles, or if a stale lockfile has been left behind by a crashed XWin which you don't have rights to remove. > > Although i have added this option, cygwinx creates the X1 File in "tmp/.X11-unix". So no other user can access cygwin while it is open. > The logbook output is then: > > ---- > Welcome to the XWin X Server > Vendor: The Cygwin/X Project > Release: 1.8.0.0 (10800000) > Build Date: 2010-04-02 > > Contact: cygwin-xfree@cygwin.com > XWin was started with the following command line: > > /usr/bin/Xwin :1 -ac -query 10.8.248.101 -clipboard -logfile C:\DOKUME~1\fltplehr\LOKALE~1\Temp\xwin.fltplehr.1.log > -nolock -dpi 75 > > ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - primary monitor w 1280 h 1024 winInitializeDefaultScreens - native DPI x 96 y 96 winInitializeDefaultScreens - Returning [1061722.984] _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 [1061722.984] _XSERVTransOpen: transport open failed for inet6/pc08309:1 [1061722.984] _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 [1061723.015] _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed [1061723.015] _XSERVTransMakeAllCOTSServerListeners: server already running [1061723.015] Fatal server error: > [1061723.015] Cannot establish any listening sockets - Make sure an X server isn't already running > ---- > > I am starting the program with the following code: > start O:\PLS_Faser\Cygwin_PLSStarter\cygwin_installed\bin\Xwin.exe :1 -ac -query IP -clipboard -logfile "%TEMP%\xwin.%USERNAME%.1.log" -nolock -dpi 75 > > Can you help me? -- 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-06-30 18:03 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-06-29 16:13 Mathias Friesenbichler 2010-06-30 18:03 ` Jon TURNEY [this message] [not found] <899957031274A04FB53CA5077F5C1367033D7A6D6F@MAILSTORE.LAG.AT> 2010-07-01 5:54 ` Mathias Friesenbichler 2010-07-01 14:45 ` 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=4C2B86E4.4040207@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).