I'll try a mock up where I submit using MY time values in sequence and see if it accepts it. As long as it will accept values in the PAST (but just later than the last PAST value) then we are good to go. I can make it work using that concept.
I was just seeing (before as i recall), that it would NOT accept values older than the last current timestamp. So, if I started with a 1352393972 as the first value submitted but NOW was 1352394572 (for example, 10 minutes difference...the lag), then an update using the time value of 1352393992 (20 seconds later in the sample time), it would complain and reject it stating that the value was prior to the last update value. Maybe I was mistaken and i fed in a time value that was indeed older (less than 1352393972). I'll recreate my test set and try it again making sure. -- View this message in context: http://rrd-mailinglists.937164.n2.nabble.com/Disabling-Last-Update-tp7580590p7580600.html Sent from the RRDtool Users Mailinglist mailing list archive at Nabble.com. _______________________________________________ rrd-users mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users
