move usdb init as per k1xx's bug

[spider.git] / txt / spiderFAQ.txt

diff --git a/txt/spiderFAQ.txt b/txt/spiderFAQ.txt
index 235ab7ccb8e1e078adfb30d56729fa10069956df..315f73cbe57812fed9b6f7712d75aba95f16c91c 100644 (file)
--- a/txt/spiderFAQ.txt
+++ b/txt/spiderFAQ.txt
@@ -1,6 +1,6 @@
   The DXSpider FAQ
-  Ian Maude, G0VGS, (ianmaude@btinternet.com)
-  $Date$ $Revision$
+  Ian Maude, G0VGS, (g0vgs@gb7mbc.net)
+  December 2001 Revision: 1.8
 
   A reference for SysOps of the DXSpider DXCluster program.
   ______________________________________________________________________
@@ -9,20 +9,20 @@
 
 
   1. Installation
-
      1.1 Where do I get DXSpider?
      1.2 How do I use the patches?
      1.3 If I use a tarball to overwrite my installation, what happens to my configuration?
      1.4 I am running RedHat 5.2 and I am getting strange errors, what is wrong?
 
   2. Administration
-
      2.1 How can I get Spider to restart automatically if it crashes?
      2.2 How can I monitor traffic to and from a node or user?
      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?
+     2.7 Since I last updated I seem to be getting duplicate spots appearing.
+     2.8 I have deleted a message but it is still there, why?
 
 
   ______________________________________________________________________
@@ -49,8 +49,6 @@
 
 
 
-
-
   assuming the patch version you are using is 1.40 and resides in /tmp!
 
 
@@ -88,7 +86,6 @@
 
 
 
-
   Run _\bt_\be_\bl_\bi_\bn_\bi_\bt _\bq 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.
@@ -105,7 +102,6 @@
 
 
 
-
   or in later versions of Spider, there is a command called _\bw_\ba_\bt_\bc_\bh_\bd_\bb_\bg in
   which case you simply type ..
 
@@ -115,8 +111,6 @@
 
 
 
-
-
   2\b2.\b.3\b3.\b.  M\bMy\by n\bne\bei\big\bgh\bhb\bbo\bou\bur\bri\bin\bng\bg n\bno\bod\bde\be c\bca\ban\bnn\bno\bot\bt u\bus\bse\be t\bth\bhe\be R\bRC\bCM\bMD\bD c\bco\bom\bmm\bma\ban\bnd\bd t\bto\bo m\bme\be,\b, h\bhe\be j\bju\bus\bst\bt
   k\bke\bee\bep\bps\bs g\bge\bet\btt\bti\bin\bng\bg t\bth\bhe\be "\b"t\btu\but\bt t\btu\but\bt"\b" m\bme\bes\bss\bsa\bag\bge\be.\b.
 
@@ -154,7 +148,6 @@
 
 
 
-
   Remember to make it executable!
 
   This will limit your debug data down to the last 10 days
@@ -178,21 +171,22 @@
   That should solve the problem.
 
 
+  2\b2.\b.7\b7.\b.  S\bSi\bin\bnc\bce\be I\bI l\bla\bas\bst\bt u\bup\bpd\bda\bat\bte\bed\bd I\bI s\bse\bee\bem\bm t\bto\bo b\bbe\be g\bge\bet\btt\bti\bin\bng\bg d\bdu\bup\bpl\bli\bic\bca\bat\bte\be s\bsp\bpo\bot\bts\bs
+  a\bap\bpp\bpe\bea\bar\bri\bin\bng\bg.\b.
 
+  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\b2.\b.8\b8.\b.  I\bI h\bha\bav\bve\be d\bde\bel\ble\bet\bte\bed\bd a\ba m\bme\bes\bss\bsa\bag\bge\be b\bbu\but\bt i\bit\bt i\bis\bs s\bst\bti\bil\bll\bl t\bth\bhe\ber\bre\be,\b, w\bwh\bhy\by?\b?
 
-
-
-
-
-
-
-
-
-
-
-
+  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
+  _\bd_\be_\bl_\be_\bt_\be_\b/_\be_\bx_\bp_\bu_\bn_\bg_\be to delete it immediately.