Tobi, What should we do about "UPDATEV" until we have support in rrdcached?
Currently the client code will just abort "UPDATEV" requests. This may cause problems in an environment that uses both "UPDATE" and "UPDATEV"... it's probably desirable to set $RRDCACEHD_ADDRESS for the former, but it's impossible for the latter. I see a couple decent options: - "FLUSH" the file, then operate directly on it (race condition with new updates?) - Implement "UPDATEV" in the daemon. How does this affect 1.4 release timing? -- kevin brintnall =~ /kbr...@rufus.net/ _______________________________________________ rrd-developers mailing list rrd-developers@lists.oetiker.ch https://lists.oetiker.ch/cgi-bin/listinfo/rrd-developers
