minor adds and changes

diff --git a/html/adminmanual-1.html b/html/adminmanual-1.html
index 1fb0df409d562287ba0b8d87a6162f032078635d..0a7924945ad3124ab4bcd84e69dffa0421ff1eb8 100644 (file)
--- a/html/adminmanual-1.html
+++ b/html/adminmanual-1.html
@@ -32,21 +32,21 @@ handle loops well at all.  It is therefore necessary to have some form
 of protection for these nodes.
 <P>
 <P>In fact DXSpider has had a simple system for some time which is called
 of protection for these nodes.
 <P>
 <P>In fact DXSpider has had a simple system for some time which is called

-<I>isolation</I>. This is similar to what, in other systems such as 
+<I>isolation</I>. This is similar to what in other systems such as 

 <B>clx</B>, is called <I>passive mode</I>. A more detailed explanation
 of <I>isolation</I> is given further below. This system is still available
 and, for simple networks, is probably all that you need.
 <P>
 <B>clx</B>, is called <I>passive mode</I>. A more detailed explanation
 of <I>isolation</I> is given further below. This system is still available
 and, for simple networks, is probably all that you need.
 <P>

-<P>The new functionality introduced in version 1.48 is filtering the node
+<P>The new functionality introduced in version 1.48 allows filtering the node

 and user protocol frames on a "per interface" basis. We call this
 <I>route filtering</I>. This is used <B>instead of</B>
 <I>isolation</I>. 
 <P>
 <P>What this really means is that you can control more or less completely
 and user protocol frames on a "per interface" basis. We call this
 <I>route filtering</I>. This is used <B>instead of</B>
 <I>isolation</I>. 
 <P>
 <P>What this really means is that you can control more or less completely

-which PC protocol frames, to do with user and node management, pass to
-each of your partner nodes. You can also limit what comes into your
-node from your partners. You can even control the settings that your
-partner node has for the routing information that it sends to you
+which user and node management PC protocol frames pass to each of your 
+partner nodes. You can also limit what comes into your node from your 
+partners. It is even possible to control the settings that your partner 
+node has for the routing information that it sends to you 

 (using the <I>rcmd</I> command).
 <P>
 <H2><A NAME="ss1.2">1.2 Route Filters</A>
 (using the <I>rcmd</I> command).
 <P>
 <H2><A NAME="ss1.2">1.2 Route Filters</A>


@@ -58,18 +58,25 @@ might suit the UK cluster network but didn't really fit anybody else.
 However using a default filter is an appropriate thing to do. How, is
 explained further on.
 <P>
 However using a default filter is an appropriate thing to do. How, is
 explained further on.
 <P>

-<P>The first thing that you must do is determine whether you need to do route filtering <B>at all</B>. If you are a "normal" node with two or three partners
-and you arranged in an "official" non-looping tree type network, then <B>you do 
-not need to do route filtering</B> and you will feel a lot better for not 
-getting involved. If you are successfully using <I>isolation</I> then you
-also probably don't need to use route filtering.
-<P>
-<P>You will only require this functionality if you are
-"well-connected". What that means is that you are connected to several
-different parts of (say) the EU cluster and, at the same time, also
-connected to two or three places in the US which, in turn are
-connected back to the EU. This is called a "loop" and if you are
-seriously looped then you need filtering.
+<P>The first thing that you must do is determine whether you need to use 
+route filtering <B>at all</B>. If you are a "normal" node with two or 
+three partners and you arranged in an "official" non-looping tree type 
+network, then <B>you do not need to do route filtering</B> and you will 
+feel a lot better for not getting involved. If you are successfully using 
+<I>isolation</I> then you also probably don't need to use route filtering.
+<P>
+<P>To put it simply, you should not mix Isolation and Route Filtering.  It 
+will work, of sorts, but you will not get the expected results.  If you 
+are using Isolation sucessfully at the moment, do not get involved in 
+Route Filtering unless you have a good supply of aspirin!  Once you have 
+started down the road of Route Filtering, do not use Isolation either.
+Use one or the other, not both.
+<P>
+<P>You will only require this functionality if you are "well-connected". What 
+that means is that you are connected to several different parts of (say) 
+the EU cluster and, at the same time, also connected to two or three places 
+in the US which, in turn are connected back to the EU. This is called a 
+"loop" and if you are seriously looped then you need filtering.

 <P>
 <P>I should at this stage give a little bit of background on filters.  All
 the filters in Spider work in basically the same way.  You can either
 <P>
 <P>I should at this stage give a little bit of background on filters.  All
 the filters in Spider work in basically the same way.  You can either


@@ -117,7 +124,8 @@ channel_zone &lt;numbers&gt;
 </PRE>
 </CODE></BLOCKQUOTE>
 <P>Please be careful if you alter this setting, it will affect 
 </PRE>
 </CODE></BLOCKQUOTE>
 <P>Please be careful if you alter this setting, it will affect 

-<B><I>ALL</I></B> your links!
+<B><I>ALL</I></B> your links!  Remember, this is a <I>default</I>
+filter for node connections, not a <I>per link</I> default.

 <P>
 <P>For the default routing filter then you have two real choices: either
 a "national" view or the "safe" option of only your own
 <P>
 <P>For the default routing filter then you have two real choices: either
 a "national" view or the "safe" option of only your own


@@ -154,9 +162,9 @@ information from anyone else. Although it doesn't explicitly say so,
 by implication, any other node information (not from the UK and Eire)
 is accepted.
 <P>
 by implication, any other node information (not from the UK and Eire)
 is accepted.
 <P>

-<P>As I imagine it will take a little while to get one's head around all of this you
-can study the effect of any rules that you try by watching the debug output
-after having done:-
+<P>As I imagine it will take a little while to get one's head around all of 
+this you can study the effect of any rules that you try by watching the 
+debug output after having done:-

 <P>
 <BLOCKQUOTE><CODE>
 <PRE>
 <P>
 <BLOCKQUOTE><CODE>
 <PRE>


@@ -191,8 +199,8 @@ accept/route &lt;node_call&gt; &lt;filter_option&gt;
 <P>
 <BLOCKQUOTE><CODE>
 <PRE>
 <P>
 <BLOCKQUOTE><CODE>
 <PRE>

-rej/route gb7djk call_dxcc 61,38 (everything except  UK+EIRE nodes)
-rej/route all     (equiv to [very] restricted mode)
+rej/route gb7djk call_dxcc 61,38 (send everything except UK+EIRE nodes)
+rej/route all                    (equiv to [very] restricted mode)

 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
 acc/route gb7djk call gb7djk     (equiv to SET/ISOLATE)
 </PRE>
 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
 acc/route gb7djk call gb7djk     (equiv to SET/ISOLATE)
 </PRE>


@@ -206,7 +214,8 @@ acc/route gb7baa all
 acc/route gb7baa input all
 </PRE>
 </CODE></BLOCKQUOTE>
 acc/route gb7baa input all
 </PRE>
 </CODE></BLOCKQUOTE>

-<P>or restricting it quite a lot, in fact making it very nearly like an <I>isolated</I> node, like this:-
+<P>or restricting it quite a lot, in fact making it very nearly like an 
+<I>isolated</I> node, like this:-

 <P>
 <BLOCKQUOTE><CODE>
 <PRE>
 <P>
 <BLOCKQUOTE><CODE>
 <PRE>


@@ -218,9 +227,9 @@ rej/route pi4ehv-8 input call_dxcc 61,38
 but only sends him my local configuration (just a PC19 for GB7DJK and
 PC16s for my local users).
 <P>
 but only sends him my local configuration (just a PC19 for GB7DJK and
 PC16s for my local users).
 <P>

-<P>It is possible to do <B>much</B> more complex rules, there are up to 10
-accept/reject pairs per callsign per filter. For more information see the 
-next section. 
+<P>It is possible to write <B>much</B> more complex rules, there are up 
+to 10 accept/reject pairs per callsign per filter. For more information 
+see the next section. 

 <P>
 <P>
 <H2><A NAME="ss1.5">1.5 General filter rules</A>
 <P>
 <P>
 <H2><A NAME="ss1.5">1.5 General filter rules</A>


@@ -552,8 +561,7 @@ 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 use
 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 use

-an <EM>acc/spot &gt;call&lt; all</EM>ilter in the
-to override the isolate. 
+an <EM>acc/spot &gt;call&lt; all</EM> filter to override the isolate. 

 <P>
 <HR>
 <A HREF="adminmanual-2.html">Next</A>
 <P>
 <HR>
 <A HREF="adminmanual-2.html">Next</A>

diff --git a/html/adminmanual-2.html b/html/adminmanual-2.html
index 25afaa266e8f6f55fb39b346a5924fafd611bf2f..f8c1071179ae58db5c4d601c019972b0f26a5884 100644 (file)
--- a/html/adminmanual-2.html
+++ b/html/adminmanual-2.html
@@ -87,7 +87,7 @@ file will then be removed.
 There are a number of commands that control whether a spot progresses
 any further by regarding it as "bad" in some way.
 <P>
 There are a number of commands that control whether a spot progresses
 any further by regarding it as "bad" in some way.
 <P>

-<P>A DX Spot has a number of fields which can checked to see whether they
+<P>A DX Spot has a number of fields which can be checked to see whether they

 contain "bad" values, they are: the DX callsign itself, the Spotter and
 the Originating Node.
 <P>
 contain "bad" values, they are: the DX callsign itself, the Spotter and
 the Originating Node.
 <P>

diff --git a/html/adminmanual-4.html b/html/adminmanual-4.html
index 37ff648b53ad8efaf2a2bd64c8a4b50cff9364ab..a54fa8ceb29de474306fad4952140af5aedcee30 100644 (file)
--- a/html/adminmanual-4.html
+++ b/html/adminmanual-4.html
@@ -24,7 +24,7 @@ any legal command for a callsign or class of connection which will be executed
 at logon.
 <P>
 <P> 
 at logon.
 <P>
 <P> 

-The filename are the callsign of the connection that you want the script to 
+The filename is the callsign of the connection that you want the script to 

 operate on, eg: <EM>/spider/scripts/g1tlh</EM>. The filenames are always in 
 lower case on those architectures where this makes a difference.
 <P>
 operate on, eg: <EM>/spider/scripts/g1tlh</EM>. The filenames are always in 
 lower case on those architectures where this makes a difference.
 <P>

diff --git a/html/adminmanual-7.html b/html/adminmanual-7.html
index f75cfd19ef37182bde6930c88846fbb8d66b78c2..50f14cdbfcaf19b9004276fee5e19ad0476aa448 100644 (file)
--- a/html/adminmanual-7.html
+++ b/html/adminmanual-7.html
@@ -21,13 +21,9 @@ at
 that it is possible to update your DXSpider installation to the latest
 sources by using a few simple commands.
 <P>
 that it is possible to update your DXSpider installation to the latest
 sources by using a few simple commands.
 <P>

-<P>THIS IS NOT FOR THE FAINT HEARTED!!!  ONLY DO THIS IF YOU HAVE A TEST
-INSTALLATION OR ARE WILLING TO HAVE YOUR CLUSTER CRASH ON YOU!!!
-THIS MUST BE CONSIDERED AT LEAST BETA TESTING AND MAYBE EVEN ALPHA!!
-YOU HAVE BEEN WARNED!!!
-<P>
-<P>DID I MENTION..... ONLY DO THIS IF YOU ARE WILLING TO ACCEPT THE
-CONSEQUENCES!!!
+<P>Please be aware that if you update your system using CVS, it is possible that
+you could be running code that is very beta and not fully tested.  There is
+a possibility that it could be unstable.

 <P>
 <P>I am of course assuming that you have a machine with both DXSpider and
 Internet access running.
 <P>
 <P>I am of course assuming that you have a machine with both DXSpider and
 Internet access running.

diff --git a/html/adminmanual.html b/html/adminmanual.html
index fc56acbf2fcf5656cb09ef43f8b43ab0bf30d0a8..0951c93cc7050fdec31f38ee499a96984f388209 100644 (file)
--- a/html/adminmanual.html
+++ b/html/adminmanual.html
@@ -15,7 +15,7 @@ Contents
 <HR>
 <H1>The DXSpider Administration Manual v1.48</H1>
 
 <HR>
 <H1>The DXSpider Administration Manual v1.48</H1>
 

-<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>Version 1.48 August 2001 revision 1.1
+<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>Version 1.48 September 2001 revision 1.2

 <P><HR>
 <EM>A reference for SysOps of the DXSpider DXCluster program.</EM>
 <HR>
 <P><HR>
 <EM>A reference for SysOps of the DXSpider DXCluster program.</EM>
 <HR>

diff --git a/sgml/adminmanual.sgml b/sgml/adminmanual.sgml
index d6fb29940ca80701b12555b89ae1fed1aa24cd66..f075b7988bb9a35e03316d921e811fe9350b3e60 100644 (file)
--- a/sgml/adminmanual.sgml
+++ b/sgml/adminmanual.sgml
@@ -6,7 +6,7 @@
 
 <title>The DXSpider Administration Manual v1.48</title> 
 <author>Ian Maude, G0VGS, (ianmaude@btinternet.com)</author>
 
 <title>The DXSpider Administration Manual v1.48</title> 
 <author>Ian Maude, G0VGS, (ianmaude@btinternet.com)</author>

-<date>Version 1.48 August 2001 revision 1.1</date>
+<date>Version 1.48 September 2001 revision 1.2</date>

 
 <abstract>
 A reference for SysOps of the DXSpider DXCluster program.
 
 <abstract>
 A reference for SysOps of the DXSpider DXCluster program.


@@ -37,23 +37,23 @@ of protection for these nodes.
 
 <P>
 In fact DXSpider has had a simple system for some time which is called
 
 <P>
 In fact DXSpider has had a simple system for some time which is called

-<it>isolation</it>. This is similar to what, in other systems such as 
+<it>isolation</it>. This is similar to what in other systems such as 

 <bf>clx</bf>, is called <it>passive mode</it>. A more detailed explanation
 of <it>isolation</it> is given further below. This system is still available
 and, for simple networks, is probably all that you need.
 
 <P>
 <bf>clx</bf>, is called <it>passive mode</it>. A more detailed explanation
 of <it>isolation</it> is given further below. This system is still available
 and, for simple networks, is probably all that you need.
 
 <P>

-The new functionality introduced in version 1.48 is filtering the node
+The new functionality introduced in version 1.48 allows filtering the node

 and user protocol frames on a "per interface" basis. We call this
 <it>route filtering</it>. This is used <bf>instead of</bf>
 <it>isolation</it>. 
 
 <p>
 What this really means is that you can control more or less completely
 and user protocol frames on a "per interface" basis. We call this
 <it>route filtering</it>. This is used <bf>instead of</bf>
 <it>isolation</it>. 
 
 <p>
 What this really means is that you can control more or less completely

-which PC protocol frames, to do with user and node management, pass to
-each of your partner nodes. You can also limit what comes into your
-node from your partners. You can even control the settings that your
-partner node has for the routing information that it sends to you
+which user and node management PC protocol frames pass to each of your 
+partner nodes. You can also limit what comes into your node from your 
+partners. It is even possible to control the settings that your partner 
+node has for the routing information that it sends to you 

 (using the <it>rcmd</it> command).
 
 <sect1>Route Filters
 (using the <it>rcmd</it> command).
 
 <sect1>Route Filters


@@ -66,19 +66,27 @@ However using a default filter is an appropriate thing to do. How, is
 explained further on.
 
 <p>
 explained further on.
 
 <p>

-The first thing that you must do is determine whether you need to do route filtering <bf>at all</bf>. If you are a "normal" node with two or three partners
-and you arranged in an "official" non-looping tree type network, then <bf>you do 
-not need to do route filtering</bf> and you will feel a lot better for not 
-getting involved. If you are successfully using <it>isolation</it> then you
-also probably don't need to use route filtering.
+The first thing that you must do is determine whether you need to use 
+route filtering <bf>at all</bf>. If you are a "normal" node with two or 
+three partners and you arranged in an "official" non-looping tree type 
+network, then <bf>you do not need to do route filtering</bf> and you will 
+feel a lot better for not getting involved. If you are successfully using 
+<it>isolation</it> then you also probably don't need to use route filtering.

 
 <p>
 
 <p>

-You will only require this functionality if you are
-"well-connected". What that means is that you are connected to several
-different parts of (say) the EU cluster and, at the same time, also
-connected to two or three places in the US which, in turn are
-connected back to the EU. This is called a "loop" and if you are
-seriously looped then you need filtering.
+To put it simply, you should not mix Isolation and Route Filtering.  It 
+will work, of sorts, but you will not get the expected results.  If you 
+are using Isolation sucessfully at the moment, do not get involved in 
+Route Filtering unless you have a good supply of aspirin!  Once you have 
+started down the road of Route Filtering, do not use Isolation either.
+Use one or the other, not both.
+
+<p>
+You will only require this functionality if you are "well-connected". What 
+that means is that you are connected to several different parts of (say) 
+the EU cluster and, at the same time, also connected to two or three places 
+in the US which, in turn are connected back to the EU. This is called a 
+"loop" and if you are seriously looped then you need filtering.

 
 <P>
 I should at this stage give a little bit of background on filters.  All
 
 <P>
 I should at this stage give a little bit of background on filters.  All


@@ -125,7 +133,8 @@ channel_zone &lt;numbers&gt;
 </verb></tscreen>
 
 Please be careful if you alter this setting, it will affect 
 </verb></tscreen>
 
 Please be careful if you alter this setting, it will affect 

-<bf><it>ALL</it></bf> your links!
+<bf><it>ALL</it></bf> your links!  Remember, this is a <it>default</it>
+filter for node connections, not a <it>per link</it> default.

 
 <p>
 For the default routing filter then you have two real choices: either
 
 <p>
 For the default routing filter then you have two real choices: either


@@ -164,9 +173,9 @@ by implication, any other node information (not from the UK and Eire)
 is accepted.
 
 <p>
 is accepted.
 
 <p>

-As I imagine it will take a little while to get one's head around all of this you
-can study the effect of any rules that you try by watching the debug output
-after having done:-
+As I imagine it will take a little while to get one's head around all of 
+this you can study the effect of any rules that you try by watching the 
+debug output after having done:-

 
 <tscreen><verb>
 set/debug filter
 
 <tscreen><verb>
 set/debug filter


@@ -196,8 +205,8 @@ accept/route &lt;node_call&gt; &lt;filter_option&gt;
 Here are some examples of route filters ...
 
 <tscreen><verb>
 Here are some examples of route filters ...
 
 <tscreen><verb>

-rej/route gb7djk call_dxcc 61,38 (everything except  UK+EIRE nodes)
-rej/route all     (equiv to [very] restricted mode)
+rej/route gb7djk call_dxcc 61,38 (send everything except UK+EIRE nodes)
+rej/route all                    (equiv to [very] restricted mode)

 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
 acc/route gb7djk call gb7djk     (equiv to SET/ISOLATE)
 </verb></tscreen>
 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
 acc/route gb7djk call gb7djk     (equiv to SET/ISOLATE)
 </verb></tscreen>


@@ -210,7 +219,8 @@ acc/route gb7baa all
 acc/route gb7baa input all
 </verb></tscreen>
 
 acc/route gb7baa input all
 </verb></tscreen>
 

-or restricting it quite a lot, in fact making it very nearly like an <it>isolated</it> node, like this:-
+or restricting it quite a lot, in fact making it very nearly like an 
+<it>isolated</it> node, like this:-

 
 <tscreen><verb>
 acc/route pi4ehv-8 call gb7djk
 
 <tscreen><verb>
 acc/route pi4ehv-8 call gb7djk


@@ -222,9 +232,9 @@ but only sends him my local configuration (just a PC19 for GB7DJK and
 PC16s for my local users).
 
 <p>
 PC16s for my local users).
 
 <p>

-It is possible to do <bf>much</bf> more complex rules, there are up to 10
-accept/reject pairs per callsign per filter. For more information see the 
-next section. 
+It is possible to write <bf>much</bf> more complex rules, there are up 
+to 10 accept/reject pairs per callsign per filter. For more information 
+see the next section. 

 
 
 <sect1>General filter rules
 
 
 <sect1>General filter rules


@@ -553,8 +563,7 @@ 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 use
 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 use

-an <em>acc/spot &gt;call&lt; all</em filter in the
-to override the isolate. 
+an <em>acc/spot &gt;call&lt; all</em> filter to override the isolate. 

 
 <sect>Other filters
 
 
 <sect>Other filters
 


@@ -630,7 +639,7 @@ There are a number of commands that control whether a spot progresses
 any further by regarding it as "bad" in some way.
 
 <p>
 any further by regarding it as "bad" in some way.
 
 <p>

-A DX Spot has a number of fields which can checked to see whether they
+A DX Spot has a number of fields which can be checked to see whether they

 contain "bad" values, they are: the DX callsign itself, the Spotter and
 the Originating Node.
 
 contain "bad" values, they are: the DX callsign itself, the Spotter and
 the Originating Node.
 


@@ -875,7 +884,7 @@ any legal command for a callsign or class of connection which will be executed
 at logon.
 
 <p> 
 at logon.
 
 <p> 

-The filename are the callsign of the connection that you want the script to 
+The filename is the callsign of the connection that you want the script to 

 operate on, eg: <em>/spider/scripts/g1tlh</em>. The filenames are always in 
 lower case on those architectures where this makes a difference.
 
 operate on, eg: <em>/spider/scripts/g1tlh</em>. The filenames are always in 
 lower case on those architectures where this makes a difference.
 


@@ -1349,14 +1358,9 @@ that it is possible to update your DXSpider installation to the latest
 sources by using a few simple commands.
 
 <P>
 sources by using a few simple commands.
 
 <P>

-THIS IS NOT FOR THE FAINT HEARTED!!!  ONLY DO THIS IF YOU HAVE A TEST
-INSTALLATION OR ARE WILLING TO HAVE YOUR CLUSTER CRASH ON YOU!!!
-THIS MUST BE CONSIDERED AT LEAST BETA TESTING AND MAYBE EVEN ALPHA!!
-YOU HAVE BEEN WARNED!!!
-
-<P>
-DID I MENTION..... ONLY DO THIS IF YOU ARE WILLING TO ACCEPT THE
-CONSEQUENCES!!!
+Please be aware that if you update your system using CVS, it is possible that
+you could be running code that is very beta and not fully tested.  There is
+a possibility that it could be unstable.

 
 <P>
 I am of course assuming that you have a machine with both DXSpider and
 
 <P>
 I am of course assuming that you have a machine with both DXSpider and

diff --git a/sgml/spiderFAQ.sgml b/sgml/spiderFAQ.sgml
index 2e53a4124bb8a8798a1f0c15c0ec8368ffc324da..a34a1efae599164879951257b3f1af01f04a0fb9 100644 (file)
--- a/sgml/spiderFAQ.sgml
+++ b/sgml/spiderFAQ.sgml
@@ -139,4 +139,12 @@ few steps to correct the problem.
 
 That should solve the problem.
 
 
 That should solve the problem.
 

+<sect1>Since I last updated I seem to be getting duplicate spots appearing.
+
+<P>
+What has probably happened is that the dupefile has got corrupted in
+some way.  Simply delete the /spider/data/dupefile and restart the
+cluster.  It may take a little time to become fully functional but
+should solve your problem.
+

 </article>
 </article>