X-Git-Url: http://gb7djk.dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=txt%2FspiderFAQ.txt;h=f32efc22ae92ff6d2a168985839819de08827657;hb=96f91d83613b6351322d818f349137e457cb0168;hp=6d79590b19e4d78dbffed9f92578b05f64e3ab8f;hpb=4c81b3f1cd138370d5ca232d95a5b2793bc22c88;p=spider.git diff --git a/txt/spiderFAQ.txt b/txt/spiderFAQ.txt index 6d79590b..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.3 January 2001 + Ian Maude, G0VGS, (g0vgs@gb7mbc.net) + December 2001 Revision: 1.8 A reference for SysOps of the DXSpider DXCluster program. ______________________________________________________________________ @@ -21,6 +21,10 @@ 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? ______________________________________________________________________ @@ -57,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?? @@ -64,6 +71,7 @@ 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?? @@ -122,7 +130,6 @@ reset the home_node using the _s_p_o_o_f command like this .. - spoof gb7adx set/home gb7adx @@ -130,6 +137,7 @@ 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?? @@ -139,6 +147,64 @@ 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. + + + 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. + + + + + +