[FreeNX-kNX] FreeNX: What is the file nxclient good for?

[Fabian Franz]

> Fabian Franz wrote:
> > If we could, we would have done that a long time ago ...
> > 
> > Well, it needs to be called nxclient, because nxagent is searching for
> that exact file in path with option dialog. I dunno why the hell they did
> not just call it nxdialog and then run it via nxclient ...
> > 
> > Its just another one of those annoying things NX ships hardcoded with.
> 
> I don't know where on earth you found that the path of nxclient binary
> is hardcoded. Please, could you point me to the code where it is done?

Sorry, I have to apologize and do apologize here.

FreeNX was based originally on 1.3.2, which clearly had this hardcoded. 

I had overlooked the entry in the ChangeLog that this had been changed.
("due to the developer down time, which you clearly addressed in another KB article")

Of course as soon as I would have tried to implement it, I would see that it was changed and the $NX_CLIENT is a good solution.

Sorry, for the disinformation and FUD.

Still we will fork NX, because it gives the possibility to work with a stable branch of the software, so we can have a BASELINE like NoMachine has too and merge needed bugfixes and new features.

Also we won't whine then anymore, but just implement or change things we don't like.

I apologize again. I should have known better.

cu

Fabian