[FreeNX-kNX] Re: Re: Re: Re: connection timeout

[Gian Filippo Pinzari]

Roie Kerstein wrote:
> Warning: Couldn't invoke 'nxclient'. Error is 2 'No such file or directory'.
> Warning: Trying with path
> '/usr/NX/bin:/opt/NX/bin:/usr/local/NX/bin:/usr/kde/3.3/bin:/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/3.4.3:/usr/X11R6/bin:/opt/blackdown-jdk-1.4.2.01/bin:/opt/blackdown-jdk-1.4.2.01/jre/bin:/usr/qt/3/bin:/usr/kde/3.3/bin:/usr/games/bin:/usr/share/karamba/bin'.
> Info: Aborting procedure due to signal '15'.
> 
> It is quite wierd, because nxclient is in /usr/NX/bin/ but nxproxy claims
> that it is not there...

It doesn't claim that it is not there. It first tries to invoke the
'nxclient' executable that is in the current path. If this fails, it
then tries again after having added '/usr/NX/bin' to the path. This
works, presumably, as I can't see a second error.

The warning says that nxproxy had to explicitly add the well-known
directories, while an usable nxclient was supposed to be in the
system path.

The reason why nxproxy is running nxclient --dialog is to inform
the user that couldn't establish the connection yet. This is just
a visual feedback given to the user and would not cause the session
to fail. The process that is killing nxproxy is nxclient, when the
timeout arises.

/Gian Filippo.