X-Git-Url: http://gb7djk.dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2FspiderFAQ-2.html;h=417b5e15aa2174e568417ee092bacb6b4514f0e1;hb=dea6cbc282b2c101672139c9369af8c9bba7122e;hp=9cd41a3ccfcd6d8deac0b2c7274f444a307c4cd8;hpb=685da1fc8aebf1b363b16e2664c90dc6eb9ac7a1;p=spider.git diff --git a/html/spiderFAQ-2.html b/html/spiderFAQ-2.html index 9cd41a3c..417b5e15 100644 --- a/html/spiderFAQ-2.html +++ b/html/spiderFAQ-2.html @@ -2,9 +2,10 @@ - The DXSpider FAQ : Administration + The DXSpider FAQ: Administration + Next @@ -63,25 +64,37 @@ spoof gb7adx set/home gb7adx

There is a file in /spider/msg called forward.pl.issue. Rename this to -forward.pl and edit it to meet your requirements. To make the changes -take effect, use the command load/forward. +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 I have set up my partner node with bulletin mail. Now I am sending -him all my bulletins! How do I stop it?

+

2.5 How can I automatically limit the amount of debug logfiles that are stored? +

-

Unless you tell Spider otherwise, when you set a node up as a forwarding -partner it will send all the mail with the bulletin addresses you have -configured. To stop this happening you need to tell the cluster that -all mail has already been sent. To do this use the catchup command. +

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 The WWV command does not seem to work.. why is that? +

2.6 I updated my Linux distribution and now Spider cannot read the users file or the dupefile, what is the problem?

-

The WWV command is not supported in DXSpider. This decision has been -taken as there is a perfectly good automated and accurate WWV posting made -once per hour from N4TY. In the past, inaccurate postings have been made -from some users and this will prevent this happening. +

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


Next Previous