On Sun, Nov 19, 2006 at 10:07:47AM +1100, Rob Conway wrote:
> ## Aquarium PH GRAPH ##
> rrdtool graph /website/ph1d.png --start e-1d --end $etime \
> --upper-limit 8.0 --lower-limit 6.2 --units-length 2 \
> --rigid --slope-mode --width 426 --height 200 \
> --title "pH" --vertical-label "PH" --in
Thanks for the input guy's
I converted my end time however the generation of 6 graphs still takes 30
seconds on my 266 mhz processor. The script below only shows one rrdtool
graph statement however the other 5 graphs statements are the same. Is
there anything else I can do to optimise the gra
On Sat, Nov 18, 2006 at 09:32:15AM +, Simon Hobson wrote:
> Rob Conway wrote:
>
> >I just use "date +%s" to get the unix time but how can I easily
> >round this value ?
>
> etime=`date +%s`
> step=300
> etime=$(( ${etime} - ( ${etime} % ${step} ) ))
etime=$(( ${etime} / ${step} * ${step} )
Hi Simon,
I would use
perl -e 'print "".localtime(time - time % 300)'
> Rob Conway wrote:
>
> >I just use "date +%s" to get the unix time but how can I easily
> >round this value ?
>
> etime=`date +%s`
> step=300
> etime=$(( ${etime} - ( ${etime} % ${step} ) ))
>
> Now, can someone show me ho
Rob Conway wrote:
>I just use "date +%s" to get the unix time but how can I easily
>round this value ?
etime=`date +%s`
step=300
etime=$(( ${etime} - ( ${etime} % ${step} ) ))
Now, can someone show me how to convert the resulting end time to a
human readable form - eg so I can use it in a gpri
