- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Administration Manual v1.48: Other filters</TITLE>
+ <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
+ <TITLE>The DXSpider Administration Manual v1.50: Other filters</TITLE>
<LINK HREF="adminmanual-3.html" REL=next>
<LINK HREF="adminmanual-1.html" REL=previous>
<LINK HREF="adminmanual.html#toc2" REL=contents>
<LINK HREF="adminmanual-3.html" REL=next>
<LINK HREF="adminmanual-1.html" REL=previous>
<LINK HREF="adminmanual.html#toc2" REL=contents>
<P>I think this is fairly self explanatory. It is simply a list of subject
headers that we do not want to pass on to either the users of the cluster or
the other cluster nodes that we are linked to. This is usually because of
<P>I think this is fairly self explanatory. It is simply a list of subject
headers that we do not want to pass on to either the users of the cluster or
the other cluster nodes that we are linked to. This is usually because of
-rules and regulations pertaining to items for sale etc in a particular country.
-<P>
-<P>
-<H2><A NAME="ss2.2">2.2 Filtering words from text fields in Announce, Talk and DX spots</A>
+rules and regulations pertaining to items for sale etc in a particular country.</P>
+
+
+<H2><A NAME="ss2.2">2.2</A> <A HREF="adminmanual.html#toc2.2">Filtering words from text fields in Announce, Talk and DX spots</A>
</H2>
<P>From version 1.48 onwards the interface to this has changed. You can now
use the commands <EM>set/badword</EM> to add words that you are not prepared
to see on the cluster, <EM>unset/badword</EM> to allow that word again and
</H2>
<P>From version 1.48 onwards the interface to this has changed. You can now
use the commands <EM>set/badword</EM> to add words that you are not prepared
to see on the cluster, <EM>unset/badword</EM> to allow that word again and
<P>If you have a previous <EM>/spider/data/badwords</EM>, the first time you start
the node, it will read and convert this file to the new commands. The old style
<P>If you have a previous <EM>/spider/data/badwords</EM>, the first time you start
the node, it will read and convert this file to the new commands. The old style
-file will then be removed.
-<P>
-<H2><A NAME="ss2.3">2.3 Stopping (possibly bad) DX Spots from Nodes or Spotters</A>
+file will then be removed.</P>
+
+<H2><A NAME="ss2.3">2.3</A> <A HREF="adminmanual.html#toc2.3">Stopping (possibly bad) DX Spots from Nodes or Spotters</A>
-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
+any further by regarding it as "bad" in some way.</P>
+
+<P>A DX Spot has a number of fields which can be checked to see whether they
<P>These work in the same as the <EM>set/badword</EM> command, you can add
any words or callsigns or whatever to the appropriate database. For
<P>These work in the same as the <EM>set/badword</EM> command, you can add
any words or callsigns or whatever to the appropriate database. For
<P>You can remove a word using the appropriate unset command
(<EM>unset/baddx, unset/badspotter, unset/badnode</EM>) or list them
using one of <EM>show/baddx, show/badspotter</EM> and
<P>You can remove a word using the appropriate unset command
(<EM>unset/baddx, unset/badspotter, unset/badnode</EM>) or list them
using one of <EM>show/baddx, show/badspotter</EM> and