X-Git-Url: http://scm.dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;ds=sidebyside;f=sgml%2FspiderFAQ.sgml;h=67d2c8ecca59deec4ba44d53d0aad233145a160b;hb=8b94259b7a3e97751662280d0cbd606ff7a68e1e;hp=2dc5a0a51a431a6525882c96938aa3778c614329;hpb=4c81b3f1cd138370d5ca232d95a5b2793bc22c88;p=spider.git
diff --git a/sgml/spiderFAQ.sgml b/sgml/spiderFAQ.sgml
index 2dc5a0a5..67d2c8ec 100644
--- a/sgml/spiderFAQ.sgml
+++ b/sgml/spiderFAQ.sgml
@@ -6,7 +6,7 @@
The DXSpider FAQ
Ian Maude, G0VGS, (ianmaude@btinternet.com)
-Version 0.3 January 2001
+Version 0.5 March 2001
A reference for SysOps of the DXSpider DXCluster program.
@@ -111,5 +111,32 @@ forward.pl and edit it to meet your requirements. You will need to issue
the command load/forward or restart Spider for the changes to
take effect.
+How can I automatically limit the amount of debug logfiles that are stored?
+
+
+Use the tmpwatch command. Create a file in /etc/cron.daily/ containing the line ...
+
+
+/usr/sbin/tmpwatch -f 240 /spider/data/debug
+
+
+Remember to make it executable!
+
+This will limit your debug data down to the last 10 days
+
+I updated my Linux distribution and now Spider cannot read the users file or the dupefile, what is the problem?
+
+
+Almost certainly this is a change in the db format of perl. Follow these
+few steps to correct the problem.
+
+
+- stop the cluster (disable any autostart in inittab)
+
- cd /spider/data
+
- issue the command perl user_asc
+
- restart the cluster
+
+
+That should solve the problem.