The biggest problems with big config files is that if one process hangs, it may take too long before the rest of the entries in your config file are processed. Hence -> NaNs in your database.
Multiple config files are also less messy and you can start them after each other in your crontab, instead of your server having to do a lot of work to do every 5 minutes. Something like: 1-59/5 * * * * mrtg config1.cfg 2-59/5 * * * * mrtg config2.cfg 3-59/5 * * * * mrtg config3.cfg spreads the load. Serge. > Right now my MRTG homepage > is mess as I have one giant config file. I spoke to a friend about > this and he said to break each server into its own config > file and then > call them individually. Would this work? -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/rrd-users WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
