Alex :
What I was trying to say is that when I specified a epoch time which fell on exactly HH:MM:00 and not HH:MM:26 (ie. had seconds aswell) it worked. Yes, I understand my fetch syntax was incorrect and should have just specified the -s <epoch_time> option only. Alex van den Bogaerdt <[EMAIL PROTECTED]> on 10/10/2002 12:17:29 To: [email protected] cc: (bcc: Phil Daws/UKDPS/DEBISFSREG2) Subject: [rrd-users] Re: RRD Fetch always shows Nan On Thu, Oct 10, 2002 at 10:45:13AM +0100, [EMAIL PROTECTED] wrote: > # /opt/rrdtool-1.0.33/bin/rrdtool update /portal/content/mrtg/appresponse.rrd > 1033456800:23364 > # /opt/rrdtool-1.0.33/bin/rrdtool fetch /portal/content/mrtg/appresponse.rrd MAX > -s 1033456603 -e 1033456603 > login > > 1033456500: nan > 1033456800: 2.3364000000e+04 So what is it. First you say rrdtool fetch *always* returns NaN now you show that isn't true. Don't shoot the messenger: You still need to grasp the basics of rrdtool. RTFM, the tutorial and the faq site. One of the questions I didn't keep in the quoted text asked for something that, IMHO, is explained multiple times in all three mentioned resources. Querying "-s 1033456603 -e 1033456603" on a database with "--step 300" shows that you don't know what you're doing. Alex -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/rrd-users WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi ****************************************************************************** CONFIDENTIALITY STATEMENT This email, its content and any files transmitted with it are intended solely for the addressee(s) and may be legally privileged and/or confidential. Access by any other party is unauthorised without the express written permission of the sender. If you have received this email in error you may not copy or use the contents, attachments or information in anyway. Please destroy it and contact the sender on 0870 840 5000 or via email return. This email has been prepared using information believed by the author to be reliable and accurate, but DaimlerChrysler Services UK Ltd. makes no warranty as to accuracy or completeness. In particular DaimlerChrysler Services UK Ltd. does not accept responsibility for changes made to this email after it was sent. Any opinions expressed in this document are those of the author and do not necessarily reflect the opinions of DaimlerChrysler Services UK Ltd, or its affiliates. CONFIDENTIALITY STATEMENT ****************************************************************************** -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/rrd-users WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
