X-Git-Url: http://scm.dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;ds=inline;f=html%2FspiderFAQ-2.html;h=300b2774f7158c656923e1319742674fcd7359ca;hb=1ef2fd58669de7cae92418c4591b9fce5f66bfb0;hp=ca16815ac2daed59965b5e9ff076221d4303510d;hpb=c42f6d2e451d149bd3ee9059ed8a9a4589c47f6d;p=spider.git diff --git a/html/spiderFAQ-2.html b/html/spiderFAQ-2.html index ca16815a..300b2774 100644 --- a/html/spiderFAQ-2.html +++ b/html/spiderFAQ-2.html @@ -2,7 +2,7 @@
-+
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 +
+
Almost certainly this is a change in the db format of perl. Follow these +few steps to correct the problem. +
+
That should solve the problem. +
+
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. +
+
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 delete/expunge +to delete it immediately.