X-Git-Url: http://gb7djk.dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=sgml%2FspiderFAQ.sgml;h=2ebda13e0951d36885ce06ae551858aa16205cbd;hb=a52a4d8c59a80d66796429ef2787491581f76326;hp=c60216c7f53e517e4e3b6aace143431f66c35c61;hpb=0bbd79b480f385485ce6b0be25f9dee47e955eb1;p=spider.git diff --git a/sgml/spiderFAQ.sgml b/sgml/spiderFAQ.sgml index c60216c7..2ebda13e 100644 --- a/sgml/spiderFAQ.sgml +++ b/sgml/spiderFAQ.sgml @@ -4,9 +4,9 @@ -
-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 ...
+Almost certainly this is a change in the db format of perl. Follow these
+few steps to correct 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.
+