Add sh/c and sh/c/n and sh/connect to the user and admin manuals. Sort

[spider.git] / sgml / spiderFAQ.sgml

diff --git a/sgml/spiderFAQ.sgml b/sgml/spiderFAQ.sgml
index 2dc5a0a51a431a6525882c96938aa3778c614329..2e53a4124bb8a8798a1f0c15c0ec8368ffc324da 100644 (file)
--- 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.3 January 2001
+<title>The DXSpider FAQ</title>
+<author>Ian Maude, G0VGS, (ianmaude@btinternet.com)</author>
+<date>$Date$ $Revision$</date>
 <abstract>
 A reference for SysOps of the DXSpider DXCluster program.
 </abstract>
@@ -111,5 +111,32 @@ 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.
 
 </article>