One thing to be aware of when switching to daemon.... Any time you update an MRTG .cfg file, you will have to stop and restart the MRTG process. With straight cron, the changes will be picked up on the next polling cycle. As James points out, the .cfg file isn't read every 5 minutes..
Also, I would look at combining the other scripts you are running into a single "master" script that calls the others. As you have seen, it is loading perl and that script a bunch of times every 5 minutes. By combining into a single script that processes each config in succession, you will at least spread them out, and possibly save yourself quite a bit of overhead, depending on how you implement. Have fun! Tim Sheets Illinois Century Network Supervisor, Regions V and VI 309-671-7680 309-671-7684 (Fax) > -----Original Message----- > From: james [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 04, 2003 10:38 PM > To: Ross Tsolakidis > Cc: [EMAIL PROTECTED] > Subject: [mrtg] Re: mrtg showing very high cpu usage cause of > otherapprunning > > > Forgot to mention the advantage of running as a daemon; > 1) Saves the load of starting the app every 5 mins > 2) loading and reading the config every 5 mins > 3) Allows MRTG to fork for faster data acquisition > > > -- > 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
