[rrd-developers] rrd file access code

Tobias Oetiker tobi at oetiker.ch
Tue Oct 14 13:36:43 CEST 2008

Hi Sebastian,

Today Sebastian Harl wrote:
> > However, I notice that some other files (e.g. rrd_create.c) also have
> > code which accesses files directly (e.g. calling open() to create a
> > file).
> Imho, the currently existing code need _a_ _lot_ more abstraction in
> that respect. Having to mess around with the internal structure of RRD
> files in many places imho makes the code really hard to read and
> maintain.

> > Is there some ongoing work to centralise the file access code?  Would it
> > be worthwhile for me to patch some of this code (e.g. rrd_create.c) to
> > go through the functions in rrd_open.c, or is there some other solution
> > coming?
> Please note that there was some discussion about a new API which started
> in the thread around "rrdtool 1.4 development ready to go" [1]. There
> have been no specific suggestions so far but I know that there are a
> couple of ideas floating around out there.
> I might make sense to not put too much effort into any modifications at
> this point but rather come up with a good solution for the API first.

I agree, also when thinking about going for the new file
format while keeping support for the old one ... My problem is that
at the moment my rrdtool time gets used up by keeping 'the project'
running. So I don't see time in the next few weeks for implementing
something like this ...


Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900

More information about the rrd-developers mailing list