On Fri, Dec 13, 2002 at 06:01:50PM +0100, Markus Schaub wrote: > My current idea is a patch at the RRD calls in mrtg which > writes the arguments of the RRDs::update statements to > a file. This file is then copied onto the presenter and there > a simple perl script reads the file and executes the RRD:update > commands to keep the slave copy in sync.
Will probably work. Of course you have to write a time stamp with each of the update commands. Do not use "N" as the current time. > Regular transfers of the complete rrd file (one a day) would > ensure the copies stay in sync. Shouldn't be necessary. A check won't hurt but your update process should be able to update the slave copy just the same as the master copy is. > What do you think about this? Will this work or did I > miss any potential problems or is there an easier solution? I do recall a discussion on this list about an updater over the network. You may want to look at it, perhaps it works for you? Alex -- Much of what looks like rudeness in hacker circles is not intended to give offence. Rather, it's the product of the direct, cut-through-the-bullshit communications style that is natural to people who are more concerned about solving problems than making others feel warm and fuzzy. http://www.tuxedo.org/~esr/faqs/smart-questions.html -- 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
