[Dxspider-support] Setting maximum connections
n2ki at amsat.org
Fri Oct 3 11:53:38 BST 2008
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?
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
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
Dxspider-support mailing list
Dxspider-support at dxcluster.org
More information about the Dxspider-support