<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16608" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Hi;</DIV>
<DIV> </DIV>
<DIV>My thoughts follow with Ian but the difference I see between the Cron and RunAsdaemon would be around the timings.</DIV>
<DIV> </DIV>
<UL>
<LI>Cron setup does not rely on the scans completing before the next starts.</LI>
<LI>RunAsDaemon will depend on the Perl script deciding that the right time has passed for the next scan.</LI></UL>
<DIV>Now the Cron design also allows you to update the CFG files when every you need and not interrupt the current timings.</DIV>
<DIV> </DIV>
<DIV>Personally I prefer the Cron setup as it will also close the process and therefore reduce the full load (should make very little difference really).</DIV>
<DIV> </DIV>
<DIV>Hope this helps.</DIV>
<DIV> </DIV>
<DIV>Andrew</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>
<DIV><FONT face=Tahoma size=1>*****************************************<BR>Andrew Bowie</FONT></DIV>
<DIV><FONT face=Tahoma size=1>Principal Computer Systems Officer<BR>Public Trustee of Queensland<BR>Ph 07 3213 9177<BR>Mobile 042 302 8518<BR>Fax 07 3213 9485<BR>*****************************************</FONT></DIV><BR><BR>>>> "Brogden, Ian" <Ian.Brogden@COORS.COM> 20/02/2008 9:07 am >>><BR><BR>You need to ensure each of the cfg files can be processed in under 5<BR>minutes, even if some devices are down (this actually makes the queries<BR>take much longer, due to timeouts and retries).<BR><BR>I usually split my files to contain under 200 interfaces each, and just<BR>run multiple instances using runasdaemon, but it depends if you<BR>frequently have multiple devices down.<BR><BR>Right now, I have about a dozen running, totalling somewhere around 1000<BR>counters, on a 7 year old Dell Wintel server.<BR><BR>Ian Brogden<BR>EDS - CTO @ MolsonCoors Account<BR><BR>( Mobile Phone:+1-303-961-1850<BR>+ mailto:ian.brogden@eds.com<BR><BR>-----Original Message----!
-<BR>From: mrtg-bounces@lists.oetiker.ch<BR>[mailto:mrtg-bounces@lists.oetiker.ch] On Behalf Of Michael Silver<BR>Sent: Tuesday, February 19, 2008 3:56 PM<BR>To: mrtg@lists.oetiker.ch<BR>Subject: [mrtg] RunAsDaemon vs. cron job<BR><BR>Hello,<BR><BR>Another newbie question...<BR><BR>I want to use MRTG to track traffic patterns on 51 devices, most having<BR>6 interfaces I want to monitor. That brings us up to ~612 queries (51<BR>devices x 6 interfaces x 2 counters) assuming worst case scenarios. The<BR>machine running MRTG runs two other services - Nagios and Request<BR>Tracker. The 15 min. load averages running those services plus<BR>monitoring 3 of the above devices runs around 0.02 with 1 min. spikes as<BR>high as 0.50.<BR><BR>Given those loads, I don't think the server is going to have issues with<BR>the added snmp traffic. Still, I would like to set up MRTG to be<BR>reasonable in terms of its resources. As I see it, I could divide my<BR>devices into 5 groups, each with t!
heir own cfg file, so I can stagger<BR>the mrtg load across 5 minutes
using cron, or I could run one big cfg<BR>file using RunAsDaemon. (I guess I could run one big file and cron, but<BR>I don't see the point in that.) <BR><BR>Does anyone have any recommendations or experiences with this before I<BR>shoot myself in the foot by not seeing the obvious? I gotta admit, I'm<BR>leaning towards 5 groups and cron right now.<BR><BR>Thanks for any pointers or advice.<BR><BR>Michael<BR><BR>Michael Silver, Network Administrator<BR>Parkland Regional Library<BR>5404 56 Avenue Lacombe, AB T4L 1G1 <BR>Phone: 403.782.3850 Fax: 403.782.4650<BR>http://www.prl.ab.ca/ msilver@prl.ab.ca<BR><BR><BR>_______________________________________________<BR>mrtg mailing list<BR>mrtg@lists.oetiker.ch<BR>https://lists.oetiker.ch/cgi-bin/listinfo/mrtg<BR><BR><BR>_______________________________________________<BR>mrtg mailing list<BR>mrtg@lists.oetiker.ch<BR>https://lists.oetiker.ch/cgi-bin/listinfo/mrtg<BR><BR></DIV><br><br><table bgcolor=white style="co!
lor:black"><tr><td><br>****************************************************************************<br>
This correspondence is for the named person's use only. It may<br>
contain confidential or legally privileged information or both. No <br>
confidentiality or privilege is waived or lost by any mistransmission. <br>
If you receive this correspondence in error, please immediately<br>
delete it from your system and notify the sender. You must not <br>
disclose copy or rely on any part of this correspondence if you<br>
are not the intended recipient. Any opinions expressed in this <br>
message are those of the individual sender, except where the <br>
sender expressly, and with authority, states them to be the <br>
opinions of the Public Trustee of Queensland.<br>
****************************************************************************<br>
</td></tr></table></BODY></HTML>