X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=txt%2FspiderFAQ.txt;h=ecd962658f9b7c6a0ecbc64e19089f8082f133cb;hb=5405fc43af4410805160aed50df04bc5fc9df869;hp=6d79590b19e4d78dbffed9f92578b05f64e3ab8f;hpb=4c81b3f1cd138370d5ca232d95a5b2793bc22c88;p=spider.git diff --git a/txt/spiderFAQ.txt b/txt/spiderFAQ.txt index 6d79590b..ecd96265 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 + Version 0.4 March 2001 A reference for SysOps of the DXSpider DXCluster program. ______________________________________________________________________ @@ -21,6 +21,7 @@ 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? ______________________________________________________________________ @@ -63,7 +64,6 @@ 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?? @@ -139,22 +139,22 @@ 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