X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=txt%2FspiderFAQ.txt;h=f32efc22ae92ff6d2a168985839819de08827657;hb=8b89a9f5ce05bee89e83d68a75da9e73f560ee67;hp=142293b299d103d59d39a466f9e4e8cc33eea301;hpb=204a594bd86adeba2cbb1ddefd3ddd6c288b702a;p=spider.git

diff --git a/txt/spiderFAQ.txt b/txt/spiderFAQ.txt
index 142293b2..f32efc22 100644
--- a/txt/spiderFAQ.txt
+++ b/txt/spiderFAQ.txt
@@ -1,6 +1,6 @@
   The DXSpider FAQ
-  Ian Maude, G0VGS, (ianmaude@btinternet.com)
-  Version 0.5 March 2001
+  Ian Maude, G0VGS, (g0vgs@gb7mbc.net)
+  December 2001 Revision: 1.8
 
   A reference for SysOps of the DXSpider DXCluster program.
   ______________________________________________________________________
@@ -23,6 +23,8 @@
      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?
 
 
   ______________________________________________________________________
@@ -59,6 +61,9 @@
   first need to apply patch-1.39 and then patch-1.40.
 
 
+
+
+
   11..33..  IIff II uussee aa ttaarrbbaallll ttoo oovveerrwwrriittee mmyy iinnssttaallllaattiioonn,, wwhhaatt hhaappppeennss ttoo
   mmyy ccoonnffiigguurraattiioonn??
 
@@ -125,11 +130,11 @@
   reset the home_node using the _s_p_o_o_f command like this ..
 
 
-
        spoof gb7adx set/home gb7adx
 
 
 
+
   Assuming that the node_call you are changing is gb7adx.
 
 
@@ -160,8 +165,8 @@
   This will limit your debug data down to the last 10 days
 
 
-  22..66..  ffiillee oorr tthhee dduuppeeffiillee,, wwhhaatt iiss tthhee pprroobblleemm??  II uuppddaatteedd mmyy LLiinnuuxx
-  ddiissttrriibbuuttiioonn aanndd nnooww SSppiiddeerr ccaannnnoott rreeaadd tthhee uusseerrss
+  22..66..  II uuppddaatteedd mmyy LLiinnuuxx ddiissttrriibbuuttiioonn aanndd nnooww SSppiiddeerr ccaannnnoott rreeaadd tthhee
+  uusseerrss ffiillee oorr tthhee dduuppeeffiillee,, wwhhaatt iiss tthhee pprroobblleemm??
 
   Almost certainly this is a change in the db format of perl.  Follow
   these few steps to correct the problem.
@@ -176,6 +181,67 @@
   +o  restart the cluster
 
   That should solve the problem.
+
+
+  22..77..  SSiinnccee II llaasstt uuppddaatteedd II sseeeemm ttoo bbee ggeettttiinngg dduupplliiccaattee ssppoottss
+  aappppeeaarriinngg..
+
+  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.
+
+
+  22..88..  II hhaavvee ddeelleetteedd aa mmeessssaaggee bbuutt iitt iiss ssttiillll tthheerree,, wwhhyy??
+
+  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
+  _d_e_l_e_t_e_/_e_x_p_u_n_g_e to delete it immediately.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+