[FreeNX-kNX] freeNX server crashed, no login

[chris at ccburton.com]

olaf <olaf-linux at gmx.de> wrote on 27/04/2010 19:14:53:

> I found the error, there was a lock-file from one of my test-users in 
/tmp:
> 
> -r--r--r--  1      1008 users        11 27. Apr 17:46 .tX1005-lock 


FreeNX produces lock files with the file name format 

        /tmp/.nXUDS-lock

where UDS is the unix domain socket number or
session display as freeNX calls it.


These files do not block logins unless the range of displays is full or
two sessions simultaneously try to use the same one !!


Are you sure you are not experiencing the 4 failed logins after
reboot / upgrade or no NX logins for a long time syndrome ??

If this is the case an update won't help you without a patch so
you need not update until you run into the evdev issue . . .



> 
> I do not know how this appears, but it was the solution, after deleting 
this 
> file everything works. I found the file by looking at the time, 
> because ~17:46 
> was the time freeNX-session crashed and no login was impossible.
> 
> Maybe this would be helpful to others.
> 
> Bye
> Olaf
> ________________________________________________________________
>      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
> ________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20100428/cb61731d/attachment.html>