And actually, that's the solution. rrdtool create foo.rrd -b -100days -s # of secs in 30 days DS:...etc.. RRA:LAST:...etc..
Now you should pick the last timestamp from your rrd that exists, doing so by rrdtool dump foo.rrd. Then you update your rrd with exactly this timestamp, after about another thirty days with the next timestamp=timestamp+ # of secs in 30 days by doing rrdtool update bla bla timestamp:value. It doesn't matter if you do that after maybe 31 or 32 days, but be sure to provide the right timestamp. The secret is that it's always a rate, so take care of heartbeat and step. A good idea for your example is to take a step of 30 days and a heartbeat of 60 days. If you then provide the values with the exact timestamps you'll have that value valid for exactly thirty days. HTH, Stephan Eric Ho wrote: > actually, that's the dilemma. > let's say that I created the rrd w/: > > rrdtool create foo.rrd -b -100days -s X DS:...etc.. RRA:LAST:...etc.. > > where X = # of secs in 30 days. > > Now, if I update it w/ timestamp, T, where T may not lie at the > beginning of the month, I get strange results when I fetch foo.rrd. > -- Stephan Harren Leiter Technik AboveNet Deutschland GmbH ------------------------- Phone +49 69 90554 153 Fax +49 69 90554 111 Cell +49 173 7011126 -- 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