[FreeNX-kNX] Suggestion to test ports for conflicts
Jeffrey J. Kosowsky
freenx-knx at kosowsky.org
Sun Dec 30 23:02:17 UTC 2007
Forwarding this (along with several other postings) to the list per
Fabian's suggestion... Note: I have also previously posted a copy to
the freenx-devel list.
Jeffrey J. Kosowsky wrote at about 00:59:41 -0500 on Monday, December 10, 2007:
> When I originally started playing with multimedia on nx, I was stymied
> because the nx client kept failing to connect until I realize that
> there was a port conflict between port 8000 (DISPLAY_BASE+7000) which
> nx was trying to use for sound and some existing nasd process on my
> server. As a newbie, it took me quite a while to diagnose and fix the
> problem.
>
> This led me to wonder whether it would make sense for the nxserver
> side to look for conflicts before selecting the base.
> For example, it would use a program like 'netstat' to identify ports
> that are already in use. The logic would be something like this:
> for (base=DISPLAY_BASE; ; base++) {
> if base or base+5000 or base+7000 or base+9000 are already
> bound to a port, then break;
> }
>
> Given the need for at least 4 very specific ports, it would seem that
> the chance of collision is not insignificant and that logic like the
> above would be very useful.
Also, I now realize that you need to use port base+3000
More information about the FreeNX-kNX
mailing list