X-Git-Url: http://dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2FspiderFAQ-2.html;h=300b2774f7158c656923e1319742674fcd7359ca;hb=8e862ce4b386889bc91c34ec788df0bd1a062c6c;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 @@ - The DXSpider FAQ : Administration + The DXSpider FAQ: Administration @@ -68,6 +68,49 @@ 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.

+

2.5 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 +

+

2.6 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. +

+

+

That should solve the problem. +

+

2.7 Since I last updated I seem to be getting duplicate spots appearing. +

+ +

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. +

+

2.8 I have deleted a message but it is still there, why? +

+ +

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.

Next