The start/end times on the DEF statement are ignored if they're outside of the time range specified at the top level (rrdtool graph). And since the time range defaults to one day ago until now, any time window specified on the DEF statement prior to one day ago is ignored.
So I think the lesson is that if you use the overrides on the DEF statement, you still need to specify the time range at the global level. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davis, Jeffrey Sent: Tuesday, November 22, 2005 11:22 PM To: [email protected] Subject: [rrd-users] overriding start/end time on DEF According to the rrdtool graph documentation: DEF:<vname>=<rrdfile>:<ds-name>:<CF>[:step=<step>][:start=<time>][:end=< time>][:reduce=<CF>] I'm not having any luck overriding the start and end times by specifying them on the DEF line. It's as though it's ignoring the time reference completely. (Although I know it's reading them because if you put in a bogus time reference, the parser will error out.) Example: DEF:ds0weekly=router.rrd:ds0:AVERAGE:start=end-1h I'm using the RRDs perl module. Does the override capability work? Anyone know why the time specification would appear to be ignored? What am I doing wrong? A newbie, JD -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://lists.ee.ethz.ch/rrd-users WebAdmin http://lists.ee.ethz.ch/lsg2.cgi -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://lists.ee.ethz.ch/rrd-users WebAdmin http://lists.ee.ethz.ch/lsg2.cgi
