Hi Florian, Feb 24 Florian Forster wrote:
> From: Florian Forster <o...@noris.net> > > Add a "FETCH" command to RRDCacheD which behaves like a (simplified > version of) rrdfetch(1). > > This has advantages over calling "FLUSH" from within the "client", > especially if the daemon is accessed using a network socket. For one, it > makes it easy to separate collecting and storing of data on one side and > creating graphs on another, possibly more public server. Without this > command this is only possible using networked file systems and similar > techniques. > > When talking to an instance of RRDCacheD via a network socket, only > relative pathnames are allowed. If the RRD file is to be accessed > afterwards (why else would one call "FLUSH"?), the client has to be in a > specific directory so the *same* relative path can be used. If the file > is on a share mounted via the network, the required CWD may differ from > the CWD of the server, making developing and deploying solutions using > separated storing and graphing unnecessarily hard. > > The data can be accessed using "rrdc_fetch" which should be a drop-in > replacement for "rrd_fetch_r". This makes it easy for programs using the > RRDtool C API to use this new functionality. thanks ... added to trunk 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