[FreeNX-kNX] Suspended Session

[Stefan Kohlsmann]

> 
> I just tested this with the following scenario:
> 1) DISABLE_PERSISTENT_SESSION="tan"
> 2) Established a session as the user 'tan'
> 3) killed nxssh on the client (similar  to a network outage/disruption)
> 4) 15 seconds later, the session was automatically terminated/removed on
> the 
> server
> 
> Isn't this what you want?
> 


Yes, exactly that's it.
On my old FreeNX / Debian that works similar.
If I kill the nxssh process / poweroff client on my "new" system, it looks like this:

root at nx10:# nxserver --list
NX> 100 NXSERVER - Version 2.1.0-72 OS (GPL, using backend: 3.2.0)
NX> 127 Sessions list:

Server     Display Username        Remote IP       Session ID
------ ------- --------------- --------------- --------------------------------
127.0.0.1       1001    test       192.168.3.155   1FD2D94F846FE88D5AEB2C8D9D4894E
NX> 999 Bye

in nxserver.log the status is right:

NX> 704 Session cache: unix-kde
NX> 707 SSL tunneling: 1
NX> 1009 Session status: starting
NX> 710 Session status: running
NX> 1002 Commit
NX> 1006 Session status: running
NX> 105 bye
Bye
NX> 999 Bye
NX> 596 Error: Session  failed. Reason was: Session: Display failure detected at 'Fri May 23 13:26:22 2008'.
NX> 1009 Session status: suspending
NX> 1005 Session status: suspended

I found that "Session failed." in /usr/lib/nx/nxnode in line 843. I try to add the line : /usr/bin/nxserver --terminate $session_id (just to kill the session directly :-) ), but the nxnode runs whit out root rights :-) .
The log's are right, but die nxserver --list command show the "wrong" status, why ?
-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger