From: Tobias Oetiker <tobi@oetiker.ch>
Date: Sun, 28 Sep 2008 19:10:15 +0000 (+0000)
Subject: When -z <jitter> is specified, some updates may be timestamped up to
X-Git-Tag: 1.4.0~305
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=18286e57b4b335925419e7648f78d8d41bd7a77e;p=thirdparty%2Frrdtool-1.x.git

When -z <jitter> is specified, some updates may be timestamped up to
<jitter> seconcds in the future.  Therefore, a timeout of now+1 may not be
sufficient.  Set abs_timeout past the point where any updates are
currently specified. -- kevin brintnall



git-svn-id: svn://svn.oetiker.ch/rrdtool/trunk/program@1533 a5681a0c-68f1-0310-ab6d-d61299d08faa
---

diff --git a/src/rrd_daemon.c b/src/rrd_daemon.c
index 18b71437..f1b8f8bb 100644
--- a/src/rrd_daemon.c
+++ b/src/rrd_daemon.c
@@ -500,7 +500,7 @@ static int flush_old_values (int max_age)
   if (max_age > 0)
     cfd.abs_timeout = cfd.now - max_age;
   else
-    cfd.abs_timeout = cfd.now + 1;
+    cfd.abs_timeout = cfd.now + 2*config_write_jitter + 1;
 
   /* `tree_callback_flush' will return the keys of all values that haven't
    * been touched in the last `config_flush_interval' seconds in `cfd'.