I do the inverse of the master.cfg. I create an include.cfg and place an Include: include.cfg at the top of each of my device config files. This way you can still standardize all of the things like html, log and image directories as well as where RRDTool is installed without having to have all of your configs launched via a single process. You can then spread the configs out via cron or whatever you like in order to prevent them all from running at the same time. Also, if you are running in an M$ environment that does not allow for forks, it gives you the ability to run two (or more) configs at the same time in parallel processes.
-----Original Message----- From: Bigelow, Andrea L. [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 06, 2005 3:52 PM To: [EMAIL PROTECTED] Subject: [mrtg] Re: One Master Config versus Several My thoughts are that doing all that including in a single mrtg.cfg file eats up a lot of resources and I could make better use of what I have by spreading things around a little bit. Has anyone tried this? If so, what happened? Would this help stop overlapping processes? Or would it still have the same problem just with more files to maintain and worry about? ----------------------------- Chuck, It sounds to me like you might benefit from splitting your file into several pieces and then forcing it to sleep for about 30 seconds between files, to ensure that you're not running into race conditions. Andi -- Unsubscribe mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/mrtg FAQ http://faq.mrtg.org Homepage http://www.mrtg.org WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi -- Unsubscribe mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/mrtg FAQ http://faq.mrtg.org Homepage http://www.mrtg.org WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
