[FreeNX-kNX] freebsd porting, nxagent starts, connecting with nxclient stops

[Fabian Franz]

> OK, after not understanding the problem with poll for way to many days I
> just switched the server to using select (setting HasPoll NO in
> FreeBSD.cf)

Nice idea ;-).

> Now nxproxy -S :1000 && nxagent -display "nx/nx,link=lan:1000" :1000
> works, I can use AbiWord & inkscape flawlessly.

Whew! Great!

> But connecting with nxclient still does not work. Any tips on how to
> debug further this are very welcome!
> 
> 
> The errors I get:
> 
> #cat wontwork-1/errors         
> Loop: WARNING! Forcing flush on priority with session raw.
> Loop: WARNING! Disabling image cache with session 'session_raw' and link
> 'adsl'.
> Socket: PANIC! Failed to set TCP_NODELAY flag on FD#14 to 1. Error is 22
> 'Invalid argument'.

Hm, a panic _is_ a bad sign. Consider setting $PROXY_TCP_NODELAY = "0" in node.conf or nxloadconfig.

> As far as I know, the problem with TCP_NODELAY does not stop the server
> (it does not when manually calling nxproxy/nxagent).

Hm, first remove the nodelay to be sure its really not that one.

Second, how to debug it:

Easy:

- Change code to add a sleep 100 before actually starting the agent. (in agent_start subfunction)
- Change code to add a sleep before application startup. (in app_start subfunction)

Login, chdirectory and start nxagent by hand, then look what happens (also having a tail -f /var/log/nxserver.log running is helpful).

If that works and agent window comes up, kill the sleep before the applications ...

See if that works and then ... well just see :-)

One catch you will need to somehow provide the monitor with the necessary data (Let it read from file like in resume case) to let the remote nxproxy connect to you.

Or directly use your own nxproxy for connection ...

The idea is of course to have the exact same options and conditions for the nxagent so you can see where the problem lies ...

cu

Fabian