On Wed, Oct 18, 2006 at 10:25:40AM +0200, Sebastian Pachuta wrote: > > For timestamp 1161088500, 13*300 is a better choice, because it is exact > > match. > > For timestamp 1161088200, 3*300 is a better choice, because it is exact > > match. > > Lets try this logic on timestamp 1161018300 > > : 1161018300 = 13 * 300 * 297697 > : 1161018300 = 3 * 300 * 1290020 + 300 > : For timestamp 1161018300, 13*300 is a better choice, because it is exact > match. > > But rrdtool chooses 3*300. > Why it happens I already described in previous message.
Yes. Same problem, other instance. RRDtool is doing what you are asking it to do, not what you expect it to do. You ask for a certain time range, and you get it. In this case, the exact matching end time would mean you won't get all the data you need. (you need it, because you ask for it!) Solution: ask another question, or restructure your database (hint: rrdtool resize) Altering rrdtool to match your expectations is not good. There are milions of other users that expect rrdtool to work as intended. If rrdtool would be altered to match your expectations, this would be bad for those other users. -- Alex van den Bogaerdt http://www.vandenbogaerdt.nl/rrdtool/ -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://lists.ee.ethz.ch/rrd-users WebAdmin http://lists.ee.ethz.ch/lsg2.cgi
