Hi Kevin, Yesterday kevin brintnall wrote:
> 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?) tis will have odd effects for people who assume update to be working remotely ... > - Implement "UPDATEV" in the daemon. How does this affect 1.4 release > timing? well you estimated that it will be quite some work ... I would like to see this in 1.5 ... the 1.4rc does not seem to be causing much of an echo, so I guess I will be releasing 1.4.0 sometime next week. cheers tobi > -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland http://it.oetiker.ch t...@oetiker.ch ++41 62 775 9902 / sb: -9900 _______________________________________________ rrd-developers mailing list rrd-developers@lists.oetiker.ch https://lists.oetiker.ch/cgi-bin/listinfo/rrd-developers
