[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freenx-knx
Subject:    Re: [FreeNX-kNX] bind failed for font TCP port 11000. Error is 112
From:       "Fabian Franz" <FabianFranz () gmx ! de>
Date:       2008-04-22 18:41:32
Message-ID: 20080422184132.251050 () gmx ! net
[Download RAW message or body]

> On Saturday 19 April 2008, Jack Tanner wrote:
> > A year ago there was a discussion regarding the message "Error: Call to
> > bind failed for font TCP port 11000. Error is 112 'Address already in
> > use'." Fabian said that there was nothing he could do:
> http://news.gmane.org/find-root.php?message_id=%3c20070423150845.87830%40gm
> >x.net%3e
> >
> > This issue has now shown up in the !M knowledge base:
> >
> > http://www.nomachine.com/tr/view.php?id=TR05E01682

Nice!

> >
> > It seems that there's a server-side configuration aspect after all, and
> > perhaps there *is* something Freenx can do.

Ouch.

> 
> AFAIK there is nothing in the protocol for the client to tell the server
> that 
> it already has a session using display X, A and B so please don't use
> those 
> displays for my session. The protocol needs extending to allow this for a 
> real solution to the problem.
> 
> !M are saying that it would be possible to introduce a configuration
> option 
> for the server that adds Y to the base display number used on that server.

And we have it already in node.conf since version 0.2 or so ;-).

# The base display number from which sessions are started.
#DISPLAY_BASE=1000

But I would have never guessed that this is the problem ...


> If 
> you control several servers you could set them so that Y=0 on one, Y=10 on
> the next, 20 on the next and so on. If you select the offset carefully for
> the given number of servers and users under your control it may be
> possible 
> to remove the chance of a collision completely _for_your_servers_. If
> you're 
> a client who connects to servers run by different admins then you're
> probably 
> still stuffed.

Agree.

So, just use the according key from node.conf.

Best Wishes,

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@kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________
[prev in list] [next in list] [prev in thread] [next in thread]