I *do* think it seems more like a buffering issue than an xport issue as I said.
I think I must have first tried RRDs::xport first. I wonder why I didn't use it? I still think xport seems kind of messy--you have to wade through all that XML to get your data. But if noone has a different suggestion I will go back to trying RRDs::xport. Thanks. -----Original Message----- From: Andreas Maus [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 24, 2006 11:34 AM To: Ruttenberg, Tanya Cc: rrd-users@list.ee.ethz.ch Subject: Re: [rrd-users] Re: Printing a text report instead of a graph On Tue, Oct 24, 2006 at 11:08:30AM -0400, Ruttenberg, Tanya wrote: Hi Tanya. > I have a perl script that generates a list of around 300 rrd files and > cranks through each one, producing an xport for each one. I use > RRDp::cmd with xport. > > The main issue we've seen I posted about previously to this list in a > post called "Rrdxport issues". Ah, yes. Found that post. Hmmm ... After a very fast look at RRDp.pm it seems that it will call rrdtool directly und uses its output. Usually stdout/stdin are buffered and maybe the buffering produces this mess. (Just a wild guess ;) I used RRDs::xport inside a perl-Script for about 200 Hosts (two RRD files per host) without any problems. > It seems like it might be an output buffering issue rather than an > rrdxport issue, but I haven't been able to fix it in any case. Could you try RRDs::xport instead? It is directly linked against librrd (at least it doesn't call rrdtool directly). HTH, Andreas. P.S.: _If_ RRDs::xport work I guess you should report this bug with RRDp::cmd -- Dipl.-Ing. Andreas Maus science+computing ag System Administration Hagellocher Weg 73 mail: [EMAIL PROTECTED] 72070 Tuebingen, Germany tel.: +49 7071 9457 456 www.science-computing.de -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://lists.ee.ethz.ch/rrd-users WebAdmin http://lists.ee.ethz.ch/lsg2.cgi