<H2><A NAME="ss13.102">13.102 show/badspotter (1)</A>
</H2>
-<P><CODE><B>show/badspotter</B>Show all the bad spotters in the system</CODE>
+<P><CODE><B>show/badspotter</B> Show all the bad spotters in the system</CODE>
<P>
<P>Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
for more information.
<HR>
<H1>The DXSpider Installation and Administration Manual </H1>
-<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>Version 1.33 (Revision 3) February 2001
+<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>Version 1.33 (Revision 1.20) February 2001
<P><HR>
<EM>A reference for SysOps of the DXSpider DXCluster program.</EM>
<HR>
the command <EM>load/forward</EM> or restart Spider for the changes to
take effect.
<P>
+<H2><A NAME="ss2.5">2.5 How can I automatically limit the amount of debug logfiles that are stored?</A>
+</H2>
+
+<P>Use the tmpwatch command. Add a line in /etc/cron.daily like this ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+/usr/sbin/tmpwatch -f 240 /spider/data/debug
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>This will limit your debug data down to the last 10 days
<P>
<HR>
Next
<HR>
<H1>The DXSpider FAQ </H1>
-<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>Version 0.3 January 2001
+<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>Version 0.4 March 2001
<P><HR>
<EM>A reference for SysOps of the DXSpider DXCluster program.</EM>
<HR>
<LI><A HREF="spiderFAQ-2.html#ss2.2">2.2 How can I monitor traffic to and from a node or user?</A>
<LI><A HREF="spiderFAQ-2.html#ss2.3">2.3 My neighbouring node cannot use the RCMD command to me, he just keeps getting the "tut tut" message.</A>
<LI><A HREF="spiderFAQ-2.html#ss2.4">2.4 I do not seem to be sending any bulletin mail to my link partners, what is wrong?</A>
+<LI><A HREF="spiderFAQ-2.html#ss2.5">2.5 How can I automatically limit the amount of debug logfiles that are stored?</A>
</UL>
<HR>
<A HREF="spiderFAQ-1.html">Next</A>
<title>The DXSpider Installation and Administration Manual
<author>Ian Maude, G0VGS, (ianmaude@btinternet.com)
-<date>Version 1.33 (Revision 3) February 2001
+<date>Version 1.33 (Revision 1.20) February 2001
<abstract>
A reference for SysOps of the DXSpider DXCluster program.
</abstract>
<P>
<tt>
-<bf>show/badspotter</bf>Show all the bad spotters in the system
+<bf>show/badspotter</bf> Show all the bad spotters in the system
</tt>
<P>
<title>The DXSpider FAQ
<author>Ian Maude, G0VGS, (ianmaude@btinternet.com)
-<date>Version 0.3 January 2001
+<date>Version 0.4 March 2001
<abstract>
A reference for SysOps of the DXSpider DXCluster program.
</abstract>
the command <em>load/forward</em> or restart Spider for the changes to
take effect.
+<sect1>How can I automatically limit the amount of debug logfiles that are stored?
+
+<P>
+Use the tmpwatch command. Add a line in /etc/cron.daily like this ...
+
+<tscreen><verb>
+/usr/sbin/tmpwatch -f 240 /spider/data/debug
+</verb></tscreen>
+
+This will limit your debug data down to the last 10 days
</article>
The DXSpider Installation and Administration Manual
Ian Maude, G0VGS, (ianmaude@btinternet.com)
- Version 1.33 (Revision 3) February 2001
+ Version 1.33 (Revision 1.20) February 2001
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
1\b13\b3.\b.1\b10\b02\b2.\b. s\bsh\bho\bow\bw/\b/b\bba\bad\bds\bsp\bpo\bot\btt\bte\ber\br (\b(1\b1)\b)
- s\bsh\bho\bow\bw/\b/b\bba\bad\bds\bsp\bpo\bot\btt\bte\ber\brShow all the bad spotters in the system
+ s\bsh\bho\bow\bw/\b/b\bba\bad\bds\bsp\bpo\bot\btt\bte\ber\br Show all the bad spotters in the system
Display all the bad spotter's callsigns in the system, see
The DXSpider FAQ
Ian Maude, G0VGS, (ianmaude@btinternet.com)
- Version 0.3 January 2001
+ Version 0.4 March 2001
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
2.2 How can I monitor traffic to and from a node or user?
2.3 My neighbouring node cannot use the RCMD command to me, he just keeps getting the "tut tut" message.
2.4 I do not seem to be sending any bulletin mail to my link partners, what is wrong?
+ 2.5 How can I automatically limit the amount of debug logfiles that are stored?
______________________________________________________________________
The tarballs are designed to not overwrite your existing configuration
and can be used at any time to update your Spider software. All the
key files have the suffix .issue (eg. DXVars.pm.issue) at default.
-
1\b1.\b.4\b4.\b. I\bI a\bam\bm r\bru\bun\bnn\bni\bin\bng\bg R\bRe\bed\bdH\bHa\bat\bt 5\b5.\b.2\b2 a\ban\bnd\bd I\bI a\bam\bm g\bge\bet\btt\bti\bin\bng\bg s\bst\btr\bra\ban\bng\bge\be e\ber\brr\bro\bor\brs\bs,\b, w\bwh\bha\bat\bt i\bis\bs
w\bwr\bro\bon\bng\bg?\b?
take effect.
+ 2\b2.\b.5\b5.\b. H\bHo\bow\bw c\bca\ban\bn I\bI a\bau\but\bto\bom\bma\bat\bti\bic\bca\bal\bll\bly\by l\bli\bim\bmi\bit\bt t\bth\bhe\be a\bam\bmo\bou\bun\bnt\bt o\bof\bf d\bde\beb\bbu\bug\bg l\blo\bog\bgf\bfi\bil\ble\bes\bs t\bth\bha\bat\bt
+ a\bar\bre\be s\bst\bto\bor\bre\bed\bd?\b?
+ Use the tmpwatch command. Add a line in /etc/cron.daily like this ...
+ /usr/sbin/tmpwatch -f 240 /spider/data/debug
-
-
-
-
-
+ This will limit your debug data down to the last 10 days