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@1533 a5681a0c-68f1-0310-ab6d-d61299d08faa

diff --git a/program/src/rrd_daemon.c b/program/src/rrd_daemon.c
index 18b7143765935969a2467746ea473ab22a753a1d..f1b8f8bb5eb455fbc05e0b195569ab988cd5c45e 100644 (file)
--- a/program/src/rrd_daemon.c
+++ b/program/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'.