[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freenx-knx
Subject:    [FreeNX-kNX] about /usr/bin/nxserver and /tmp/.X$SESS_DISPLAY-lock
From:       Yves-Gaël_Chény <yves-gael.cheny () tranquil-it-systems ! fr>
Date:       2008-01-23 15:19:14
Message-ID: 47975AF2.100 () tranquil-it-systems ! fr
[Download RAW message or body]

Hi,
when i have an error during an nx connexion of anybody, sometimes, 
/tmp/.X$SESS_DISPLAY-lock is remove but not the 
/tmp/.X11-unix/X$SESS_DISPLAY
So the nxserver can't connect my client and return an error because it 
want the same socket than an over-existing socket.
Perhaps we can add

while [ -e /tmp/.X11-unix/X$SESS_DISPLAY ]
 do
let SESS_DISPLAY=$SESS_DISPLAY+1
done

after the line 1131 inside /usr/bin/nxserver to increment the display or 
add a verification procedure who remove the unused display and lock ?

regards
yves

-- 
Yves-Gaël Chény
Directeur technique

44 Boulevard des Pas Enchantés
44230 St Sébastien sur Loire
Tel : 02 40 97 62 67 - 08 73 77 24 91
GSM : 06 98 58 41 55
http://www.tranquilitsystems.com/
yves-gael.cheny@tranquil-it-systems.fr

Tranquil IT Systems . SAS 37 000 ¤


________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:
  http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/ 

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

[prev in list] [next in list] [prev in thread] [next in thread]