minor changes to admin manual to reflect perl changes etc

[spider.git] / sgml / spiderFAQ.sgml

diff --git a/sgml/spiderFAQ.sgml b/sgml/spiderFAQ.sgml
index c60216c7f53e517e4e3b6aace143431f66c35c61..67d2c8ecca59deec4ba44d53d0aad233145a160b 100644 (file)
--- a/sgml/spiderFAQ.sgml
+++ b/sgml/spiderFAQ.sgml
@@ -6,7 +6,7 @@
 
 <title>The DXSpider FAQ 
 <author>Ian Maude, G0VGS, (ianmaude@btinternet.com)
-<date>Version 0.4 March 2001
+<date>Version 0.5 March 2001
 <abstract>
 A reference for SysOps of the DXSpider DXCluster program.
 </abstract>
@@ -114,12 +114,29 @@ 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 ...
+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>