[rrd-developers] Re: proposal for getting at <last></last> via rrdcgi
Tobias Oetiker
oetiker at ee.ethz.ch
Fri Oct 1 22:04:29 MEST 1999
Today you sent me mail regarding Re: [rrd-developers] Re: proposal for...:
*> > From: Tobias Oetiker
*> > it can print the current time:
*> >
*> > <RRD::TIMESTR 'some-strftime-format' now>
*> >
*> > or the time from 3 days ago ...
*> > <RRD::TIMESTR 'some-strftime-format' now-3d>
*> >
*> > the point is that it allows you to print something like the --end argument
*> > you have defined for the graph ...
*>
*> Maybe it's just a my opinion, but I think we are talking
*> about two distinctly different pieces of functionality:
*>
*>
*> (1) pretty-printing a given time via at-style-time specs...
*>
*> <RRD::TIMESTR 'some-strftime-format' 'some-at-style-time'>
*>
*> vaguely like GNU 'date --date "some-gnu-date-style-time"'
*>
*>
*> (2) pretty printing the last update of a given RRD...
*>
*> <RRD::LAST 'some.rrd' 'some-strftime-format'>
*>
*> very much like 'rrdtool last some.rrd'.
*>
*>
*> Okay? I don't really care about (1) but I need (2) before I
*> can migrate from MRTG to my RRDtool interface.
sure ... I just think that it is pretty simple to have a single function
which does both ... you can give it either the name of an RRD or an AT-Time
descr ... (argument overloading)
cheers
tobi
*>
*> Just a thought: what about going with <RRD::TIME::TIMESTR> and
*> <RRD::TIME::LAST> or somesuch?
*>
*> later
*> steve
*> - - -
*> systems guy
*> wiscnet.net
*>
--
______ __ _
/_ __/_ / / (_) 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
--
* To unsubscribe from the rrd-developers mailing list, send a message with the
subject: unsubscribe to rrd-developers-request at list.ee.ethz.ch
More information about the rrd-developers
mailing list