X-Git-Url: http://scm.dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;ds=sidebyside;f=html%2Fadminmanual-4.html;h=3255b16cedcefce26e9f209e0886844e797ed5d2;hb=77764988d275c1f8b650f5a103ec7147d8a5d966;hp=6055f203520cb7347719ecfa3b9251ac4e929922;hpb=e1f91307fae936112a25ed7ce08f47214ecec766;p=spider.git diff --git a/html/adminmanual-4.html b/html/adminmanual-4.html index 6055f203..3255b16c 100644 --- a/html/adminmanual-4.html +++ b/html/adminmanual-4.html @@ -22,10 +22,12 @@ from it to any other networks you may be connected to (or vice versa).
In /spider/data you will find a file called hop_table.pl. This is the file that controls your hop count settings. -It has a set of default hops on the various PC frames and also a set for each node you want to alter the hops for. -You may be happy with the default settings of course, but this powerful tool can help to protect and improve the -network. The file will look something like this ... +
In /spider/data you will find a file called hop_table.pl. This is the file +that controls your hop count settings. It has a set of default hops on the +various PC frames and also a set for each node you want to alter the hops for. +You may be happy with the default settings of course, but this powerful tool +can help to protect and improve the network. The file will look something +like this ...
@@ -81,11 +83,13 @@ $def_hopcount = 5;
-
Each set of hops is contained within a pair of curly braces and contains a series of PC frame types. PC11 for example -is a DX spot. The figures here are not exhaustive but should give you a good idea of how the file works. +
Each set of hops is contained within a pair of curly braces and contains a +series of PC frame types. PC11 for example is a DX spot. The figures here +are not exhaustive but should give you a good idea of how the file works.
-
You can alter this file at any time, including whilst the cluster is running. If you alter the file during runtime, -the command load/hops will bring your changes into effect. +
You can alter this file at any time, including whilst the cluster is running. +If you alter the file during runtime, the command load/hops will +bring your changes into effect.
-
If you use isolate on a node connection you will continue to receive all information from the isolated partner, -however you will not pass any information back to the isolated node. There are times when you would like to -forward only spots across a link (maybe during a contest for example). To do this, isolate the node in the normal -way and put in a filter in the /spider/filter/spots directory to override the isolate. This filter can be very -simple and consists of just one line .... +
If you use isolate on a node connection you will continue to receive all +information from the isolated partner, however you will not pass any information +back to the isolated node. There are times when you would like to forward only +spots across a link (maybe during a contest for example). To do this, isolate +the node in the normal way and put in a filter in the /spider/filter/spots +directory to override the isolate. This filter can be very simple and consists +of just one line ....