[FreeNX-kNX] tips for killing apps when session disconnects

[Tim Jordan]

Kurt Raschke wrote:

>I would agree that in the long run FreeNX should try to detect a loss  
>of connectivity or other failure and automatically suspend the  
>session, but in any case you can run nxserver --suspend <username> to  
>suspend the session, so that you can reconnect to it.
>
>For some reason nxserver --suspend has to be run as root even if  
>you're suspending your own session; that'll pose a problem for people  
>who don't have root on the machine they're connecting to.
>
>-Kurt
>_______________________________________________
>
I tested your suggestion.  Its works after the second attempt to connect
to the suspended session.  Not sure why the first attemp does not
connect.  I turned up the logging and the only error I see is "could not
open dislplay".

> tail:
> /home/tjordan/.nx/C-RavensRoost-1008-251410E19ACC7DD520FC4D692EB23C6D/session:
> file truncated
> NX> 504 Info: Reconnection failed: Couldn't open the display.
> NX> 1005 Session status: suspended
> NX> 105 NX> 1001 Bye.
>
Thanks for the tip.

Tim