X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2FspiderFAQ-2.html;h=300b2774f7158c656923e1319742674fcd7359ca;hb=f8d23f0de888299ee510229861cbce4b6fd25e19;hp=58b26a9dfeba18ac40acc86c8c011acf802a83b4;hpb=4c81b3f1cd138370d5ca232d95a5b2793bc22c88;p=spider.git diff --git a/html/spiderFAQ-2.html b/html/spiderFAQ-2.html index 58b26a9d..300b2774 100644 --- a/html/spiderFAQ-2.html +++ b/html/spiderFAQ-2.html @@ -2,9 +2,10 @@
-+
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.