[Dxspider-support] Setting maximum connections

[Dirk Koopman G1TLH]

To summarize:

* If you connect to them (ie you have a connect script and you either
manually or automatically connect via crontab), then you need do nothing.

* If a node connects to you (via your listen port which is usually 7300 
or 8000) then you need do nothing UNLESS that node already has 8 or more 
other connections to other nodes. I call these "big" nodes.

* If a "big" node connects to you, then either you need to raise the 
default $main::maxconnect_node to a value larger than 8, or disable this 
feature completely: by setting it to 0 (using a set/var in the startup 
script), or individually set up an exception by doing a

   set/maxconnect nn <node call>.

And to remind people, this only applies if you are using 1.55 build 
0.30. And to remind other people that if you are using 0.28 or 0.29 you 
should upgrade to 0.30.

If you are using 1.55 build 0.27 or below you can ignore all of this.

Dirk

Anthony(N2KI) wrote:
> Dirk,
> 
> When I upgrade do I have to set the max connect or is it turned off?  I
> generally have 12 to 15 nodes that connect to me.
> 
> Assuming it is on I would have to list each node in the "set/maximum"
> command to allow the nodes to connect.
> 
> If a new node comes on line, how do I add it to the list with out having to
> re-enter each node with the addition of the new node?
> 
> Anthony
>  
>  
> 
> -----Original Message-----
> From: dxspider-support-bounces at dxcluster.org
> [mailto:dxspider-support-bounces at dxcluster.org] On Behalf Of Dirk Koopman
> Sent: Thursday, October 02, 2008 6:18 PM
> To: The DXSpider Support list
> Subject: [Dxspider-support] Setting maximum connections
> 
> If you have updated in the last couple of days and you are running build 
> 0.28 or 0.29, please upgrade to latest build which should be 0.30.
> 
> This will then work as advertised by checking the maximum number of 
> times a node or user is already connected to the rest of the cluster 
> cloud on INCOMING connections. As opposed to all connections which is 
> wrong (at least for now).
> 
> There is also a command to allow big nodes (ie nodes with more (default) 
> 8 node connections) to continue to connect to your node. The command is 
> (for example):
> 
> set/maxconnect 30 gb7djk ed7zab-5 pi4tue-8 wr3d db0sue-7
> 
> And you only need to use this command if you are one of these "big" 
> nodes or one of these "big" nodes connects to you (and *not* if you 
> connect to one of them).
> 
> It is, I admit, confusing, but I am back here and available to answer 
> questions...
> 
> Dirk
> 
> 
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at dxcluster.org
> http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
> 
> 
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at dxcluster.org
> http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>