RE: Problem when trying to use -nolock Option
Hi, I posted this Problem 2 Weeks ago and no one answered yet. Is there anyone who can help me? Thanks, Mathias Original-Nachricht Datum: Thu, 17 Jun 2010 08:24:03 +0200 Von: "Mathias Friesenbichler" 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. 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 (1080) 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? Thanks, Mathias -- GMX.at - Österreichs FreeMail-Dienst mit über 2 Mio Mitgliedern E-Mail, SMS & mehr! Kostenlos: http://portal.gmx.net/de/go/atfreemail -- 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/
Re: Problem when trying to use -nolock Option
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" 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 (1080) 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/
Re: Problem when trying to use -nolock Option
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. 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? Thanks, Mathias > > > -Ursprüngliche Nachricht- > Von: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-ow...@cygwin.com] > Im Auftrag von Jon TURNEY > Gesendet: Mittwoch, 30. Juni 2010 20:03 > An: cygwin-xfree@cygwin.com > Cc: hia...@gmx.at > Betreff: Re: Problem when trying to use -nolock Option > > 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" > > 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 (1080) > > 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/ > > -- Sicherer, schneller und einfacher. Die aktuellen Internet-Browser - jetzt kostenlos herunterladen! http://portal.gmx.net/de/go/atbrowser -- 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/
Re: Problem when trying to use -nolock Option
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/
