X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=txt%2FspiderFAQ.txt;h=3be1c9aadd6b5cdfdad7d9f76e06f2b0b9086f81;hb=7346d1f8129457eee2e602b36e27435141533049;hp=20cfae60ad15f06a9cc69e6a20b5e947179ffba5;hpb=b922eb1d8811f06f593a921dcb748a1ba19aaac9;p=spider.git diff --git a/txt/spiderFAQ.txt b/txt/spiderFAQ.txt index 20cfae60..3be1c9aa 100644 --- a/txt/spiderFAQ.txt +++ b/txt/spiderFAQ.txt @@ -1,6 +1,6 @@ The DXSpider FAQ Ian Maude, G0VGS, (ianmaude@btinternet.com) - Version 0.2 July 2000 + $Date$ $Revision$ A reference for SysOps of the DXSpider DXCluster program. ______________________________________________________________________ @@ -21,6 +21,9 @@ 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. ______________________________________________________________________ @@ -60,10 +63,12 @@ 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. + 11..44.. II aamm rruunnnniinngg RReeddHHaatt 55..22 aanndd II aamm ggeettttiinngg ssttrraannggee eerrrroorrss,, wwhhaatt iiss wwrroonngg?? @@ -125,66 +130,61 @@ spoof gb7adx set/home gb7adx - - - Assuming that the node_call you are changing is gb7adx. + 22..44.. II ddoo nnoott sseeeemm ttoo bbee sseennddiinngg aannyy bbuulllleettiinn mmaaiill ttoo mmyy lliinnkk ppaarrtt-- nneerrss,, wwhhaatt iiss wwrroonngg?? There is a file in /spider/msg called forward.pl.issue. Rename this to forward.pl and edit it to meet your requirements. You will need to - restart Spider for the changes to take effect. - - - - - - - - - - - - - - - - - - - - - - - - - - + issue the command _l_o_a_d_/_f_o_r_w_a_r_d or restart Spider for the changes to + take effect. + 22..55.. HHooww ccaann II aauuttoommaattiiccaallllyy lliimmiitt tthhee aammoouunntt ooff ddeebbuugg llooggffiilleess tthhaatt + aarree ssttoorreedd?? + Use the tmpwatch command. Create a file in /etc/cron.daily/ + containing the line ... + /usr/sbin/tmpwatch -f 240 /spider/data/debug + Remember to make it executable! + This will limit your debug data down to the last 10 days + 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. + +o stop the cluster (disable any autostart in inittab) + +o cd /spider/data + +o issue the command perl user_asc + +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.