Cool, thanks Travis, Yes I have worked out all of this.
I am pleased now it is working - so now am just learning how to use the various rrdtool methods. Cheers Mark Travis Spencer wrote: > > On 2/6/07, Mark Easton <[EMAIL PROTECTED]> wrote: >> Gosh the C api is a closely guarded secret it seems. > > I wouldn't say that. Almost everything that you need to know is at > http://oss.oetiker.ch/rrdtool/doc/index.en.html. The only real > secrets have been discussed on this and the developer list before. > This is what I've picked up: > > 1. Free any double pointers you pass into RRD upon success > 2. Lock other threads out before calling any of RRD's function if > you're running in a multithreaded environment and calling a > non-reentrant version of an RRD function > 3. Clear optint, opterr, and call rrd_clear_error before invoking an > RRD function > 4. All RRD functions return a non-zero value on failure and zero upon > success. > 5. You can call rrd_test_error to find out more when something goes wrong. > 6 Ask here if you get stuck ;-) > > Did I miss any? > > See > https://lists.oetiker.ch/pipermail/rrd-developers/2006-July/001729.html > for a few more details. Also, I would suggest that you subscribe to > the lists with a gmail account or something, so you can search them > easily. (That's what I do anyway.) > > Happy hacking, Mark. > > -- > > Regards, > > Travis Spencer > > _______________________________________________ > rrd-users mailing list > [email protected] > https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users > > -- View this message in context: http://www.nabble.com/C-API--tf3182497.html#a8880310 Sent from the RRDTool - User mailing list archive at Nabble.com. _______________________________________________ rrd-users mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users
