From bdc2552d39834c58fd06e18272ba653726f59e6f Mon Sep 17 00:00:00 2001 From: g0vgs Date: Thu, 20 Sep 2001 12:33:32 +0000 Subject: [PATCH] add FAQ on dupefile --- txt/spiderFAQ.txt | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/txt/spiderFAQ.txt b/txt/spiderFAQ.txt index 235ab7cc..3be1c9aa 100644 --- a/txt/spiderFAQ.txt +++ b/txt/spiderFAQ.txt @@ -23,6 +23,7 @@ 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. ______________________________________________________________________ @@ -62,6 +63,7 @@ 11..33.. IIff II uussee aa ttaarrbbaallll ttoo oovveerrwwrriittee mmyy iinnssttaallllaattiioonn,, wwhhaatt hhaappppeennss ttoo mmyy ccoonnffiigguurraattiioonn?? + 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. @@ -128,8 +130,6 @@ spoof gb7adx set/home gb7adx - - Assuming that the node_call you are changing is gb7adx. @@ -178,13 +178,13 @@ 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. -- 2.34.1