[rrd-developers] Re: RRDp Problem With Non-existent RRD

[Tobias Oetiker]

Friday you sent me mail regarding [rrd-developers] RRDp Problem With...:

*> 
*> Problem: (RRDp rrdtools-1.0.10)
*> 
*> 	Calling RRDp::cmd "fetch file.rrd ...", where file.rrd does not
*> exist, results in an error message to *stderr* and an exit from the calling
*> perl script.  Is this appropriate behavior?  The above call is followed by a
*> call to RRDp::read and an RRDp::end where the return value would be checked
*> for an error indication.  Why not return the error indication instead of
*> blasting out?

please use the RRDs interface ... RRDp is mostly of debugging ... 

cheers
tobi



-- 
 ______    __   _
/_  __/_  / /  (_) Oetiker, Timelord & SysMgr @ EE-Dept ETH-Zurich
 / // _ \/ _ \/ / TEL: +41(0)1-6325286  FAX:...1517  ICQ: 10419518 
/_/ \.__/_.__/_/ oetiker at ee.ethz.ch http://ee-staff.ethz.ch/~oetiker

--
Unsubscribe mailto:rrd-developers-request at list.ee.ethz.ch?subject=unsubscribe
Help        mailto:rrd-developers-request at list.ee.ethz.ch?subject=help
Archive     http://www.ee.ethz.ch/~slist/rrd-developers