1. protect against PC41s with field[3] == field[2]

[spider.git] / txt / spiderFAQ.txt

diff --git a/txt/spiderFAQ.txt b/txt/spiderFAQ.txt
index de1fcd4dac4ec6678e8d1a0e6f405c1ab9002fb3..235ab7ccb8e1e078adfb30d56729fa10069956df 100644 (file)
--- a/txt/spiderFAQ.txt
+++ b/txt/spiderFAQ.txt
@@ -1,6 +1,6 @@
   The DXSpider FAQ
   Ian Maude, G0VGS, (ianmaude@btinternet.com)
-  Version 0.4 March 2001
+  $Date$ $Revision$
 
   A reference for SysOps of the DXSpider DXCluster program.
   ______________________________________________________________________
@@ -22,6 +22,7 @@
      2.3 My neighbouring node cannot use the RCMD command to me, he just keeps getting the "tut tut" message.
      2.4 I do not seem to be sending any bulletin mail to my link partners, what is wrong?
      2.5 How can I automatically limit the amount of debug logfiles that are stored?
+     2.6 I updated my Linux distribution and now Spider cannot read the users file or the dupefile, what is the problem?
 
 
   ______________________________________________________________________
@@ -64,6 +65,8 @@
   The tarballs are designed to not overwrite your existing configuration
   and can be used at any time to update your Spider software.  All the
   key files have the suffix .issue (eg. DXVars.pm.issue) at default.
+
+
   1\b1.\b.4\b4.\b.  I\bI a\bam\bm r\bru\bun\bnn\bni\bin\bng\bg R\bRe\bed\bdH\bHa\bat\bt 5\b5.\b.2\b2 a\ban\bnd\bd I\bI a\bam\bm g\bge\bet\btt\bti\bin\bng\bg s\bst\btr\bra\ban\bng\bge\be e\ber\brr\bro\bor\brs\bs,\b, w\bwh\bha\bat\bt i\bis\bs
   w\bwr\bro\bon\bng\bg?\b?
 
@@ -127,9 +130,9 @@
 
 
 
-
   Assuming that the node_call you are changing is gb7adx.
 
+
   2\b2.\b.4\b4.\b.  I\bI d\bdo\bo n\bno\bot\bt s\bse\bee\bem\bm t\bto\bo b\bbe\be s\bse\ben\bnd\bdi\bin\bng\bg a\ban\bny\by b\bbu\bul\bll\ble\bet\bti\bin\bn m\bma\bai\bil\bl t\bto\bo m\bmy\by l\bli\bin\bnk\bk p\bpa\bar\brt\bt-\b-
   n\bne\ber\brs\bs,\b, w\bwh\bha\bat\bt i\bis\bs w\bwr\bro\bon\bng\bg?\b?
 
@@ -142,7 +145,8 @@
   2\b2.\b.5\b5.\b.  H\bHo\bow\bw c\bca\ban\bn I\bI a\bau\but\bto\bom\bma\bat\bti\bic\bca\bal\bll\bly\by l\bli\bim\bmi\bit\bt t\bth\bhe\be a\bam\bmo\bou\bun\bnt\bt o\bof\bf d\bde\beb\bbu\bug\bg l\blo\bog\bgf\bfi\bil\ble\bes\bs t\bth\bha\bat\bt
   a\bar\bre\be s\bst\bto\bor\bre\bed\bd?\b?
 
-  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 ...
 
 
 
@@ -151,31 +155,27 @@
 
 
 
-  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
 
 
+  2\b2.\b.6\b6.\b.  I\bI u\bup\bpd\bda\bat\bte\bed\bd m\bmy\by L\bLi\bin\bnu\bux\bx d\bdi\bis\bst\btr\bri\bib\bbu\but\bti\bio\bon\bn a\ban\bnd\bd n\bno\bow\bw S\bSp\bpi\bid\bde\ber\br c\bca\ban\bnn\bno\bot\bt r\bre\bea\bad\bd t\bth\bhe\be
+  u\bus\bse\ber\brs\bs f\bfi\bil\ble\be o\bor\br t\bth\bhe\be d\bdu\bup\bpe\bef\bfi\bil\ble\be,\b, w\bwh\bha\bat\bt i\bis\bs t\bth\bhe\be p\bpr\bro\bob\bbl\ble\bem\bm?\b?
 
+  Almost certainly this is a change in the db format of perl.  Follow
+  these few steps to correct the problem.
 
 
+  +\bo  stop the cluster (disable any autostart in inittab)
 
+  +\bo  cd /spider/data
 
+  +\bo  issue the command perl user_asc
 
+  +\bo  restart the cluster
 
+  That should solve the problem.