[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freenx-knx
Subject:    Re: [FreeNX-kNX] Bug: negotiating link parameters -> timeout ON
From:       "Fabian Franz" <FabianFranz () gmx ! de>
Date:       2007-04-23 16:33:52
Message-ID: 20070423163352.87840 () gmx ! net
[Download RAW message or body]

>   I did something a little silly but it works. I feel like I should
> apologize... sorry:

:-)

Why apologize?

>   I added this line to the top of the nxserver script:
> 
> pstree -p nx| perl -e '@lines=<STDIN>; foreach $line  (@lines){if
> ($line=~/^sshd\((\d+)\)$/) { kill 9, $1;}}'

Haha, that is a nice hack ;-).

> 
> This line does the pstree, pipe it to perl, which in turn find the
> lines that have this and only this on it 'sshd(number)', and kills the
> processes with that number. The stubborn process gets to live after
> the first suspend, which is not so good, but it gets killed before the
> next resume is done, so it is good enough for that resume to succeed.

That gives me an idea. Try the following - if you want to:

-exec $COMMAND_NETCAT [...]
+$COMMAND_NETCAT [...]
+kill $PPID # Lets kill our parent sshd process
+           # or kill -9
+exit 0

(Of course the above is just for SSL encrypted sessions).

cu

Fabian
________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:
  http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/ 

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX@kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________
[prev in list] [next in list] [prev in thread] [next in thread]