X-Git-Url: http://www.dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=sgml%2FspiderFAQ.sgml;h=2ebda13e0951d36885ce06ae551858aa16205cbd;hb=bccf827cfc80f9871efc8a25f9bb69f99c771d77;hp=4943c47091a79351e2bebbf5d7dfb6c50802a179;hpb=564548091fc1c40f493d4bcdc104a4ce3b2ded51;p=spider.git

diff --git a/sgml/spiderFAQ.sgml b/sgml/spiderFAQ.sgml
index 4943c470..2ebda13e 100644
--- a/sgml/spiderFAQ.sgml
+++ b/sgml/spiderFAQ.sgml
@@ -4,9 +4,9 @@
 
 <!-- Title information -->
 
-<title>The DXSpider FAQ 
-<author>Ian Maude, G0VGS, (ianmaude@btinternet.com)
-<date>Version 0.2 July 2000
+<title>The DXSpider FAQ</title>
+<author>Ian Maude, G0VGS, (g0vgs@gb7mbc.net)</author>
+<date>December 2001 Revision: 1.8</date>
 <abstract>
 A reference for SysOps of the DXSpider DXCluster program.
 </abstract>
@@ -107,7 +107,53 @@ Assuming that the node_call you are changing is gb7adx.
 
 <P>
 There is a file in /spider/msg called forward.pl.issue.  Rename this to
-forward.pl and edit it to meet your requirements.  You will need to restart
-Spider for the changes to take effect.
+forward.pl and edit it to meet your requirements.  You will need to issue
+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.  Create a file in /etc/cron.daily/ containing the line ...
+
+<tscreen><verb>
+/usr/sbin/tmpwatch -f 240 /spider/data/debug
+</verb></tscreen>
+
+Remember to make it executable!
+
+This will limit your debug data down to the last 10 days
+
+<sect1>I updated my Linux distribution and now Spider cannot read the users file or the dupefile, what is the problem?
+
+<P>
+Almost certainly this is a change in the db format of perl.  Follow these
+few steps to correct the problem.
+
+<itemize>
+<item>stop the cluster (disable any autostart in inittab)
+<item>cd /spider/data
+<item>issue the command perl user_asc
+<item>restart the cluster
+</itemize>
+
+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.
+
+<sect1>I have deleted a message but it is still there, why?
+
+<P>
+This is now the way messages are handled for deletion in Spider.  If you
+look closely you will see a 'D' following the message number.  This 
+message is marked for deletion and will be deleted in 2 days if nothing
+further is done.  Optionally you can use the command <em>delete/expunge</em>
+to delete it immediately.
 
 </article>