X-Git-Url: http://gb7djk.dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2FspiderFAQ-2.html;h=4f15b247e157c39c4c43b71859a7e28d65f7a4af;hb=25270ac4d9d486c2749515c8b8f32e223d4f38b7;hp=300b2774f7158c656923e1319742674fcd7359ca;hpb=8e862ce4b386889bc91c34ec788df0bd1a062c6c;p=spider.git diff --git a/html/spiderFAQ-2.html b/html/spiderFAQ-2.html index 300b2774..4f15b247 100644 --- a/html/spiderFAQ-2.html +++ b/html/spiderFAQ-2.html @@ -1,7 +1,7 @@
- +Put this line into /etc/inittab .. +
Put this line into /etc/inittab ..
DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop > /dev/tty7
+
Run telinit q as root. Spider will restart so be aware. However, any -time you reboot, cluster.pl will start in tty7 and if it crashes, it should restart ok. -
-
There are 2 ways to achieve this. You can use the tail command like this .. +
There are 2 ways to achieve this. You can use the tail command like this ..
tail -f /spider/data/debug/167.dat |grep G0VGS
+
or in later versions of Spider, there is a command called watchdbg in which -case you simply type .. +case you simply type ..
watchdbg G0VGS
--
Assuming that the permissions are set correctly (perm level 5 required), it could be that the home_node is set incorrectly. You can reset the home_node using the spoof -command like this .. +command like this ..
spoof gb7adx set/home gb7adx
-Assuming that the node_call you are changing is gb7adx. -
-
Assuming that the node_call you are changing is gb7adx.
+ +There is a file in /spider/msg called forward.pl.issue. Rename this to 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. -
-
Use the tmpwatch command. Create a file in /etc/cron.daily/ containing the line ... +
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 -
-
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. +few steps to correct the problem.
That should solve 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. -
+to delete it immediately.
+