[FreeNX-kNX] Intended suspend isn't properly resumable

[Durk Strooisma]

> So to be sure:
>
> Ther is a nxssh process still running _and_ in that same session log
> there is a Session terminated?

Yep, after hitting "Suspend", one nxssh.exe is still alive and this is what
I'm getting in the new session log file:

Info: Display running with pid '2192' and handler '0x14f074e'.
NXPROXY - Version 2.1.0

Copyright (C) 2001, 2006 NoMachine.
See http://www.nomachine.com/ for more information.

Info: Proxy running in client mode with pid '192'.
Session: Starting session at 'Fri Feb 16 17:26:15 2007'.
Info: Synchronizing local and remote caches.
Info: Handshaking with remote proxy completed.
Info: Using adsl link parameters 512/24/1/0.
Info: Using cache parameters 4/4194304/8192KB/8192KB.
Info: Using image streaming parameters 50/128/1024KB/2048/256.
Info: Using image cache parameters 1/1/32768KB.
Info: Using pack method 'no-pack' with session 'unix-kde'.
Info: Using ZLIB data compression 3/3/0.
Info: Using ZLIB stream compression 6/6.
Info: No suitable cache file found.
Info: Listening for font server connections on port '11000'.
Session: Session started at 'Fri Feb 16 17:26:15 2007'.
Info: Established X server connection.
Info: Using shared memory parameters 1/2048K.
Session: Terminating session at 'Fri Feb 16 17:26:36 2007'.
Info: End of NX transport requested by remote.
Info: Shutting down the NX transport.
Session: Session terminated at 'Fri Feb 16 17:26:36 2007'.

> Okay, I need more info:
>
> Do:
>
> - Setup the scenario with hanging nxssh
> - Again confirm that in session log there is already a "session
> terminated" written

Tried again, refer to above piece of text.

> - Get output from server:
>
> ptree -p -u user

kdeinit(20073)─┬─kdeinit(20078)
               ├─kdeinit(20098)
               ├─kdeinit(20105)
               └─kdeinit(20111)───bash(20112)

kdeinit(20076)

kdeinit(20081)

kdeinit(20087)

kdeinit(20094)

kdeinit(20097)

kdeinit(20101)

kdeinit(20102)

kdeinit(20104)

kdeinit(20107)

korgac(20110)

bash(18749)───su(18761,root)───bash(18763)───pstree(23306)
nxnode(19884)─┬─nxnode(20032)─┬─nxnode(20033)───nxagent(20035)              │               ├─nxnode(20038)
              │               └─tee(20037)
              └─nxnode(20039)───startkde(20050)───kwrapper(20095)
> and
>
> pstree -p -u nx # best if no other session runs on it at that moment

Done, only I was having a session running (suspended):

nxserver(19853)─┬─nxserver(19854)─┬─cat(19871)                │
└─nxserver(19870)───nxnode-login(19873)───ssh(19875)                └─nxserver(19859)

> Can it be that there is a netcat process still hanging around?
>
> Then it might be a problem of netcat not closing the connection
> directly, when it encounters socket close on remote end.

No "netcat" processes on server-side. Only a normal cat (ps -ef):

nx       19871 19854  0 17:27 ?        00:00:00 cat -

Durk