[FreeNX-kNX] Error when trying to connect to FreeNX 0.7.3 on Fedora9

jhonyl jhonyl at netscape.net
Mon Sep 29 02:33:04 UTC 2008


I just had an idea for the maintainer - Maybe, if it is possible to 
catch that error in the freenx server, then the freenx server could 
automatically touch the correct lock file so the error will not repeat 
itself, and possibly to restart everything, so for the end user the 
login in will proceed without errors.

-----Original Message-----
From: jhonyl <jhonyl at netscape.net>
To: FreeNX-kNX at kde.org
Sent: Mon, 29 Sep 2008 2:25 am
Subject: Re: [FreeNX-kNX] Error when trying to connect to FreeNX 0.7.3 
on Fedora9

Probably what Terje said is best solution.

Also there are some lock file on /tmp/.X$$$$-lock , that lock the $$$$
address.
If such a file exist then freenx will not try to use the corresponding
address.
 (e.g do $ touch /tmp/.X1010-lock )
------------------
On my server:
$ ls /tmp/.X*
/tmp/.X0-lock     /tmp/.X1002-lock  /tmp/.X1005-lock  /tmp/.X1009-lock
/tmp/.X1000-lock  /tmp/.X1003-lock  /tmp/.X1007-lock
/tmp/.X1001-lock  /tmp/.X1004-lock  /tmp/.X1008-lock

/tmp/.X11-unix:
X0  X1000  X1001  X1002  X1003  X1004  X1005  X1007  X1008  X1009

----
and a code snip from /usr/NX/bin/nxserver:
--------
while [ -e /tmp/.X$SESS_DISPLAY-lock -o -e "/tmp/.nX$SESS_DISPLAY-lock"
 -o -e "/tmp/.X11-unix/X$SESS_DISPLAY" ]
 do
                let SESS_DISPLAY=$SESS_DISPLAY+1
 done
--------



-----Original Message-----
From: Terje Andersen <terander at guard.zapto.org>
To: User Support for FreeNX Server and kNX
 Client <freenx-knx at kde.org>
Sent: Sun, 28 Sep 2008 10:19 pm
Subject: Re: [FreeNX-kNX] Error when trying to connect to FreeNX 0.7.3
on Fedora9

On sø., 2008-09-28 at 20:41 +0200, Odin Nøsen wrote:
> Error: Call to bind failed for TCP port 6010. Error is 98 'Address
> already in use'.
> Error: Aborting session with 'Unable to open display

Looks like the port your session got was (TCP/6010) in use. You should
investigate what program uses that port.

If this program needs to run on that program,20please look in the
node.conf and change the base-port to avoid the port/range this program
uses.

Regards,
Terje

________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________


________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/Be
rliosProject:FreeNX_-_FAQ

         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________





More information about the FreeNX-kNX mailing list