Re: [rrd-developers] [PATCH] RRDCacheD: Add the FETCH command.

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

Re: [rrd-developers] [PATCH] RRDCacheD: Add the FETCH command.

Hi Tobi, On Wed, Feb 24, 2010 at 11:04:39PM +0100, Tobias Oetiker wrote: Add a FETCH command to RRDCacheD which behaves like a (simplified version of) rrdfetch(1). [...] I guess it's time to branche again ... I like your aproach to integrating this functionality into rrdgraph via the

Re: [rrd-developers] [PATCH] RRDCacheD: Add the FETCH command.

Hi Florian, Today Florian Forster wrote: Hi Tobi, On Wed, Feb 24, 2010 at 11:04:39PM +0100, Tobias Oetiker wrote: Add a FETCH command to RRDCacheD which behaves like a (simplified version of) rrdfetch(1). [...] I guess it's time to branche again ... I like your aproach to

[rrd-developers] [PATCH] RRDCacheD: Add the FETCH command.

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

Re: [rrd-developers] [PATCH] RRDCacheD: Add the FETCH command.

Hi Tobi, On Wed, Feb 24, 2010 at 11:04:39PM +0100, Tobias Oetiker wrote: I like your aproach to integrating this functionality into rrdgraph via the daemon argument ... (have not yet looked at the code) ... thanks :) I chose it for its simplicity and flexibility. Since there are already several