Hi Greg, I guess this will help:
Index: parsetime.c =================================================================== --- parsetime.c (revision 895) +++ parsetime.c (working copy) @@ -839,6 +839,7 @@ case NUMBER: try(tod(ptv)) try(day(ptv)) + try(tod(ptv)) break; /* fix month parsing */ case JAN: case FEB: case MAR: case APR: case MAY: case JUN: cheers tobi Today Greg Bailey wrote: > I had an application break when moving from rrdtool 1.0.X to 1.2.X, and > after escaping the colon characters in the COMMENT sections of rrdgraph, > I discovered another inconsistency. I'd been using timestamps of the > form "20060918 13:20" as a start and/or end time in rrdfetch, and while > this used to work in rrdtool 1.0.50, it stopped working in the newer > version. > > The man page for rrdfetch gives lots of example time specifications, > including: > > 19970703 12:45 -- 12:45 July 3th, 1997 (my favorite, and its > even got an ISO number (8601)). > > But that invocation gives an error for me: > > # rrdtool fetch FastEthernet0-21.rrd AVERAGE -e '19970703 12:45' > ERROR: end time: unparsable trailing text: '...12:45' > > But switching the "TIME OF DAY" and the "DAY" references gives: > > # rrdtool fetch FastEthernet0-21.rrd AVERAGE -e '12:45 19970703' > ifInOctets ifOutOctets > > 867888000: nan nan > 867974400: nan nan > > So it seems the documentation for AT STYLE TIME SPECIFICATIONS could be > updated with legal examples, and it might be worth adding a note to the > RRDTOOL 1.2 NEWS page. > > thanks, > Greg Bailey > > -- > Unsubscribe mailto:[EMAIL PROTECTED] > Help mailto:[EMAIL PROTECTED] > Archive http://lists.ee.ethz.ch/rrd-developers > WebAdmin http://lists.ee.ethz.ch/lsg2.cgi > > -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten http://tobi.oetiker.ch [EMAIL PROTECTED] ++41 62 213 9902 -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://lists.ee.ethz.ch/rrd-developers WebAdmin http://lists.ee.ethz.ch/lsg2.cgi