[rrd-developers] Bug#497739: rrdtool: rrdgraph no longer drops all directories given in filename argument when imginfo string prints

[Tobias Oetiker]

Sebastian,

it is a bug ... fixed in svn ...

cheers
tobi


Today Sebastian Harl wrote:

> tags 497739 + upstream
> thanks
>
> Hi,
>
> (This is a follow-up to Debian bug #497739. See [1] for more details.)
>
> [1] http://bugs.debian.org/497739
>
> On Wed, Sep 03, 2008 at 03:57:54PM -0700, bardia wrote:
> > I'm using rrdcgi from rrdtool to plot sensor data on my website via the sensord
> > generating rrdcgi script.  The printed "IMG SRC" path is now broken b/c the
> > directories in the filename path aren't being pruned.  The expected behavior of
> > rrdgraph is mentioned in the rrdcgi man page but not in the rrdgraph man page.
> >
> > Below is an example rrd line from the rrdcgi script that i pulled out to run
> > directly on the command line using two different versions of rrdtool:
> >
> > !!**command line:
> > rrdtool graph /var/www/sensors/pics/castledaily-temperature.png --imginfo '<IMG SRC=/sensors/pics/%s WIDTH=%lu HEIGHT=%lu>' -a PNG -h 200 -w 800 --lazy -v 'Temperature (C)' -t 'Temperature' -x 'HOUR:1:HOUR:3:HOUR:3:0:%b %d %H:00' -s -1d -l 0 DEF:temp1=/var/www/sensors/data/castle.rrd:temp1:AVERAGE DEF:temp1_0=/var/www/sensors/data/castle.rrd:temp1_0:AVERAGE DEF:temp2=/var/www/sensors/data/castle.rrd:temp2:AVERAGE DEF:loadavg=/var/www/sensors/data/castle.rrd:loadavg:AVERAGE LINE2:temp1#6e980e:"Core0 Temp" LINE2:temp1_0#aff9e7:"M/B Temp" LINE2:temp2#8897c8:"CPU Temp" LINE2:loadavg#7cfcce:"Load Average"
> >
> > !!** _GOOD_ output (rrdtool version 1.2.27-2):
> > <IMG SRC=/sensors/pics/castledaily-temperature.png WIDTH=897 HEIGHT=279>
> >
> > !!** _BAD_ output (rrdtool version 1.3.1-3):
> > <IMG SRC=/sensors/pics//var/www/sensors/pics/castledaily-temperature.png WIDTH=897 HEIGHT=274>
> >
> > There are easy ways to workaround this problem aside from reverting to ver 1.2,
> > e.g., string replacement, so i'm too lazy to look at the sources and submit a
> > patch, sorry.
>
> I'm not sure about the behavior intended by upstream and the motivation
> for changing it from 1.2 to 1.3. With this message, I've forwarded the
> bug the upstream developers mailing list, hoping for a comment.
>
> Cheers,
> Sebastian
>
>

-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900