https://bugzilla.novell.com/show_bug.cgi?id=401366 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|FRENX connection timeout on session resume with |FREENX connection timeout on session resume with |nxclient (nomachine.com) |nxclient (nomachine.com) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=401366 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Priority|P5 - None |P2 - High Summary|FREENX connection timeout on session resume with|FreeNX connection timeout on session resume with |nxclient (nomachine.com) |nxclient (nomachine.com) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=401366 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=401366#c3 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #3 from Stefan Dirsch 2008-07-21 03:06:44 MDT --- Are you sure that this doesnt kill other sessions as well by accident? Please comment. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=401366 User madworm_de.novell@spitzenpfeil.org added comment https://bugzilla.novell.com/show_bug.cgi?id=401366#c5 --- Comment #5 from robert spitzenpfeil 2008-07-21 05:02:17 MDT --- I've tested this: client 1 (user A) ----> server 1, session 1 client 2 (user A) ----> server 1, session 2 both sessions could be disconnected + resumed with this line added to nxserver. but I can't verify whether it is well behaved or not, I doubt it. the perl script just kills all sshd run with uid 'nx'. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=401366 User madworm_de.novell@spitzenpfeil.org added comment https://bugzilla.novell.com/show_bug.cgi?id=401366#c7 --- Comment #7 from robert spitzenpfeil 2008-07-21 05:35:38 MDT --- nope, 2 users don't interfere. it seems I also don't quite understand how nxserver is called (or when). the behaviour is this: without the _line_ added, sshd tasks accumulate with every resumed session, again and again. with the _line_ added, nx-sshd task related to user A gets killed as soon as the session is suspended (per session), nx-sshd of user B is unaffected. the tasks do not get killed when a session is resumed (as I thought they would be). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=401366 User madworm_de.novell@spitzenpfeil.org added comment https://bugzilla.novell.com/show_bug.cgi?id=401366#c9 --- Comment #9 from robert spitzenpfeil 2008-07-21 07:47:20 MDT --- ah, getting closer. the _relevant_ later hanging sshd daemoni/daemons ? all run as user NX. before nx session: root 3430 1 /usr/sbin/sshd -o PidFile=/var/run/sshd.init.pid root 18727 3430 sshd: spitzenpfeil [priv] 1000 18739 18727 sshd: spitzenpfeil@notty root 23985 3430 sshd: root@pts/0 during nx session: root 3430 1 /usr/sbin/sshd -o PidFile=/var/run/sshd.init.pid root 18727 3430 sshd: spitzenpfeil [priv] 1000 18739 18727 sshd: spitzenpfeil@notty root 23985 3430 sshd: root@pts/0 root 28128 3430 sshd: nx [priv] nx 28133 28128 sshd: nx@notty <-- killed by the _line_ root 28503 3430 sshd: guest [priv] guest28533 28503 sshd: guest@notty /usr/bin/nxserver is always run as user NX. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=401366 User madworm_de.novell@spitzenpfeil.org added comment https://bugzilla.novell.com/show_bug.cgi?id=401366#c11 --- Comment #11 from robert spitzenpfeil 2008-07-21 08:36:13 MDT --- as it runs as nx, it _may_ kill any other process running as nx. nxclients running on linux (from nomachine.com) do NOT exhibit this problem. active sessions always look like this with pstree (which is what the script sees): sshd(23905)---netcat(23912)---nxserver(24270)-+-nxserver(24271)-+-cat(24289) | `-nxserver(24287)---nxnode-login(24290)---ssh(24291) `-nxserver(24272) "dead" sshd are only caused by disconnecting from the windows version. this ends up with a sshd like this: sshd(22571) the regex in the perl script explicitly looks for this (pseudo code): line starts with: sshd ( some digits, but at leats 1 digit, remember the digits ends with: ) right after the digits, nothing else in between conclusion: properly disconnected sessions don't cause zombie sshds --> no problem running sessions don't match with the regex --> no problem improperly disconnected sessions leave a sshd behing that should have exited anyway, thus it is safe to kill. this and only this case matches with the regex in the script. --> should be safe. more questions dr. watson ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.