[FreeNX-kNX] Bug: negotiating link parameters -> timeout ON resume session. v.0.6.0/2.1.0-17

[torrr com]

Hi,

  I tried the proposed change to nxserver, but it didn't help. The
stubborn sshd was still there after suspend, and the subsequent resume
timed out.

On 4/20/07, Fabian Franz <FabianFranz at gmx.de> wrote:
> Thank you, I read all, but I'll just write you the short idea I had:
>
> In nxserver change:
>
> -exec $COMMAND_NETCAT $SERVER_HOST $PROXY_DISPLAY
> +$COMMAND_NETCAT $SERVER_HOST $PROXY_DISPLAY
> +exec >&-
> +exec <&-
> +exec 2>&-
> +exit 0
>
> Because the sshd must be somehow still connected to some other process via stderr or stdout or stdin.
>
> So I would try to find the process that is keeping the sshd alive.
>
> Perhaps even through ls -la /proc/<pid>/fd and finding the remote socket via netstat.
>
> Sorry for those descriptions being a bit blurry, but its still an early idea.
>
> 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 at kde.org
>       https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
>