X-Git-Url: http://www.dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=txt%2FspiderFAQ.txt;h=315f73cbe57812fed9b6f7712d75aba95f16c91c;hb=1bb3ae1a09a6117d93c02041bff9b5cd2d4819ef;hp=235ab7ccb8e1e078adfb30d56729fa10069956df;hpb=61660841afb3901002602e4956f09de5567bc950;p=spider.git diff --git a/txt/spiderFAQ.txt b/txt/spiderFAQ.txt index 235ab7cc..315f73cb 100644 --- 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 _t_e_l_i_n_i_t _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. @@ -105,7 +102,6 @@ - or in later versions of Spider, there is a command called _w_a_t_c_h_d_b_g in which case you simply type .. @@ -115,8 +111,6 @@ - - 22..33.. MMyy nneeiigghhbboouurriinngg nnooddee ccaannnnoott uussee tthhee RRCCMMDD ccoommmmaanndd ttoo mmee,, hhee jjuusstt kkeeeeppss ggeettttiinngg tthhee ""ttuutt ttuutt"" mmeessssaaggee.. @@ -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. + 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.