headers
Vaclav Vobornik | 1 Jan 2006 11:16
Picon

unicode support

Hello Tobi & All,

I've just made the decision to upgrade my old rrdtools with the actual
version because I definitely need some new great features. But it is
necessary for me to work with the unicode chars (and fonts of course). I saw
some notes about wide characters in CHANGES as well as in rrd_gfx.c but I
can't find anything in the documentation.
So my question is if there is unicode (utf-8, wide characters) support in
the actual version or do I have to use my old utf-8 patch (autumn 2004) for
that?

Thanks a lot

Vasek

PS: Happy New Year 2006 !!

--
Unsubscribe mailto:rrd-developers-request <at> list.ee.ethz.ch?subject=unsubscribe
Help        mailto:rrd-developers-request <at> list.ee.ethz.ch?subject=help
Archive     http://lists.ee.ethz.ch/rrd-developers
WebAdmin    http://lists.ee.ethz.ch/lsg2.cgi
Permalink | Reply | 1 comment |
headers
Tobias Oetiker | 2 Jan 2006 17:34
Picon
Picon
Favicon

Re: unicode support

Hi Vaclav,

the current rrdtool version supports unicode if your os does ...

cheers
tobi
Yesterday Vaclav Vobornik wrote:

> Hello Tobi & All,
>
> I've just made the decision to upgrade my old rrdtools with the actual
> version because I definitely need some new great features. But it is
> necessary for me to work with the unicode chars (and fonts of course). I saw
> some notes about wide characters in CHANGES as well as in rrd_gfx.c but I
> can't find anything in the documentation.
> So my question is if there is unicode (utf-8, wide characters) support in
> the actual version or do I have to use my old utf-8 patch (autumn 2004) for
> that?
>
> Thanks a lot
>
> Vasek
>
> PS: Happy New Year 2006 !!
>
> --
> Unsubscribe mailto:rrd-developers-request <at> list.ee.ethz.ch?subject=unsubscribe
> Help        mailto:rrd-developers-request <at> list.ee.ethz.ch?subject=help
> Archive     http://lists.ee.ethz.ch/rrd-developers
> WebAdmin    http://lists.ee.ethz.ch/lsg2.cgi
(Continue reading)

Permalink | Reply | 0 comments |
headers
Nicola Worthington | 8 Jan 2006 19:07

Patch to rrd_dump.c to allow output to a filename as well as stdout

Dear All,
Having never submitted a patch before, I was unsure as to where to send it
to, so I'm taking a best guess at the developers list and Tobi. Please
correct me if I'm not following protocol. :)

This is a patch to allow rrd_dump to output to a filename if a second
argument is specified. This makes life a lot easier if you want to use the
dump functionality in RRDs for example without wanting to do funky stuff
to capture the output. (Not everyone wants to do output redirection).

The TCL binding has been altered slightly to take this change in to
account since it was calling the rrd_dump_r method directly instead of
rrd_dump.

I hope this can be considered for inclusion in the next release. Please
let me know your thoughts.

Best wishes,
Nicola

--

-- 
Nicola Worthington
http://perlgirl.org.uk
nicolaw <at> arwen.tfb.net

-- Attached file removed by Ecartis and put at URL below --
-- Type: TEXT/PLAIN
-- Size: 16k (17068 bytes)
-- URL : http://lists.ee.ethz.ch/p/rrdtool-1.2.12-heds-20060108.patch
(Continue reading)

Permalink | Reply | 2 comments |
headers
Peter Stamfest | 8 Jan 2006 21:15
Picon

Re: Patch to rrd_dump.c to allow output to a filename as well as stdout

On Sun, 8 Jan 2006, Nicola Worthington wrote:

> Date: Sun, 8 Jan 2006 18:07:36 +0000 (GMT)
> From: Nicola Worthington <nicolaw <at> arwen.tfb.net>
> To: rrd-developers <at> list.ee.ethz.ch, oetiker <at> ee.ethz.ch
> Cc: heds <at> metahusky.net, nicolaw <at> cpan.org
> Subject: [rrd-developers] Patch to rrd_dump.c to allow output to a filename as
>      well as stdout
> 
> Dear All,
> Having never submitted a patch before, I was unsure as to where to send it
> to, so I'm taking a best guess at the developers list and Tobi. Please
> correct me if I'm not following protocol. :)
>
> This is a patch to allow rrd_dump to output to a filename if a second
> argument is specified. This makes life a lot easier if you want to use the
> dump functionality in RRDs for example without wanting to do funky stuff
> to capture the output. (Not everyone wants to do output redirection).
>
> The TCL binding has been altered slightly to take this change in to
> account since it was calling the rrd_dump_r method directly instead of
> rrd_dump.
>
> I hope this can be considered for inclusion in the next release. Please
> let me know your thoughts.

+    fprintf(out_file, "</rrd>\n");
      rrd_free(&rrd);
      fclose(in_file);
+    if (out_file)
(Continue reading)

Permalink | Reply | 1 comment |
headers
Nicola Worthington | 9 Jan 2006 11:53

Re: Patch to rrd_dump.c to allow output to a filename as well as stdout

On Sun, 8 Jan 2006, Peter Stamfest wrote:

> +    fprintf(out_file, "</rrd>\n");
>      rrd_free(&rrd);
>      fclose(in_file);
> +    if (out_file)
> +    {
> +      fclose(out_file);
> +    }
>      return(0);
>  }
>
> Shouldn't that check at least be (out_file != stdout)? Otherwise you'll end up
> closing stdout.
>
> peter

Yes, you're quite right. It was in fact meant to be exactly that.

Should I send again,.. who picks up patches for possible inclusion?

Nicola

--

-- 
Nicola Worthington
http://perlgirl.org.uk
nicolaw <at> arwen.tfb.net

--
Unsubscribe mailto:rrd-developers-request <at> list.ee.ethz.ch?subject=unsubscribe
(Continue reading)

Permalink | Reply | 0 comments |
headers
Nicola Worthington | 9 Jan 2006 13:19

Re: Patch to rrd_dump.c to allow output to a filename as well as stdout

On Mon, 9 Jan 2006, Peter Stamfest wrote:
> > > Shouldn't that check at least be (out_file != stdout)? Otherwise you'll
> > > end up
> > > closing stdout.
> > >
> > > peter
> >
> > Yes, you're quite right. It was in fact meant to be exactly that.
> >
> > Should I send again,.. who picks up patches for possible inclusion?
> >
>
> I would resend it (though it is rather large...) - and: Tobias picks the
> patches...

Attached :-)

>
> peter
>

--

-- 
Nicola Worthington
http://perlgirl.org.uk
nicolaw <at> arwen.tfb.net

-- Attached file removed by Ecartis and put at URL below --
-- Type: APPLICATION/x-gzip
-- Size: 3k (3583 bytes)
-- URL : http://lists.ee.ethz.ch/p/rrdtool-1.2.12-heds-20060109.patch.g
(Continue reading)

Permalink | Reply | 2 comments |
headers
Tobias Oetiker | 9 Jan 2006 19:36
Picon
Picon
Favicon

Re: Patch to rrd_dump.c to allow output to a filename as well as stdout

Hi Nicola,

thanks for your patch ... it is almost in ... I am only missing a
patch for  doc/rrddump.pod ...

cheers
tobi

> On Mon, 9 Jan 2006, Peter Stamfest wrote:
>
> > > > Shouldn't that check at least be (out_file != stdout)? Otherwise you'll
> > > > end up
> > > > closing stdout.
> > > >
> > > > peter
> > >
> > > Yes, you're quite right. It was in fact meant to be exactly that.
> > >
> > > Should I send again,.. who picks up patches for possible inclusion?
> > >
> >
> > I would resend it (though it is rather large...) - and: Tobias picks the
> > patches...
>
> Attached :-)
>
> >
> > peter
> >
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Ole Bjørn Hessen | 10 Jan 2006 01:49

never ending loop in rrd_graph


I discovered a never endring loop in rrd_graph. I'm not sure what how
to handle this thing.

draw_horizontal_grid was called with im->ygrid_scale.gridstep = 0 and
this lead to massive confusion in draw_horizontal_grid. 

The loop "for (i = sgrid; i <= egrid; i++){" in draw_horizontal_grid
was going on forever.  

Using gcc/gdb on Solaris 8 to debug this I saw that sgrid printed out
as -2147483648 and egrid was 2147483647.

The value "im->ygrid_scale.gridstep = 0" was there because that "pixel
= im->ysize / (scaledrange / ylab[i].grid)" never reached 7 in
calc_horizontal_grid so 'gridind' remained -1. A lookup at using
"gridind=-1" at ylab was no good idea since ylab[-1] was not
well-defined :-)

        im->ygrid_scale.gridstep = ylab[gridind].grid * im->magfact;

I tried to add more values to ylab and that seems to "fix" this, but I
do not have the faintes clue if this is a good or bad fix.

ylab_t ylab[]= {
        ...
    {1000.0, {1,2, 5,10}},
    {2000.0, {1,5,10,20}},
    {5000.0, {1,2, 4,10}},
    {10000.0, {1,2, 5,10}},
(Continue reading)

Permalink | Reply | 0 comments |
headers
George Coulouris | 13 Jan 2006 21:42
Picon
Favicon

rrdtool overflow with large rpn expressions?

Hello and happy new year!

It seems that large rpn expressions will overflow the rpn parser. I use 
rrdtool to aggregate data over hundreds of hosts (e.g. min/avg/max of a 
given performance metric, in this example, disk usage), and the rpn 
strings can grow quite large.

The native ability to handle *sets* of rrds would make cluster 
monitoring much easier.

Cheers,
George Coulouris
National Center for Biotechnology Information (contractor)

<---- cut here

Here's a stack dump:

#0  0xb7e0f078 in mallopt () from /lib/libc.so.6
#1  0xb7e0dbb0 in realloc () from /lib/libc.so.6
#2  0xb7fae0b3 in rpn_parse () from /usr/local/rrdtool-1.2.9/lib/librrd.so.2
#3  0xb7fa923b in rrd_parse_cdef ()
    from /usr/local/rrdtool-1.2.9/lib/librrd.so.2
#4  0xb7fa94df in rrd_graph_script ()
    from /usr/local/rrdtool-1.2.9/lib/librrd.so.2
#5  0xb7fa501c in rrd_graph () from /usr/local/rrdtool-1.2.9/lib/librrd.so.2
#6  0xb7fbec21 in HandleInputLine ()
    from /usr/local/rrdtool-1.2.9/lib/librrd.so.2
#7  0xb7fbdcf5 in main () from /usr/local/rrdtool-1.2.9/lib/librrd.so.2
#8  0xb7daf976 in __libc_start_main () from /lib/libc.so.6
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tobias Oetiker | 15 Jan 2006 14:35
Picon
Picon
Favicon

Re: [PATCH] rrdtool 1.0.50 build on Ubuntu Breezy Badger

Hi Blair,

thanks ... I am adding this to the 1.2 branch
and to the pending changes for 1.0.51

apropos ... there is an issue I am currently looking at, in
connection with 'multiple updates' ... since you wrote the original
code for this maybe you have some insight as to what is hitting us
here ... check out

http://people.ee.ethz.ch/~oetiker/webtools/rrdtool-trac/ticket/8

cheers
tobi

Nov 27 Blair Zajac wrote:

> Hello,
>
> I'm still supporting rrdtool 1.0.50 on Ubuntu Breezy Badger with gcc 4.0.2 for
> my Orca data graphing package and needed the below patch to get it to compile.
> I'm sending this here for future reference in case anybody has trouble compiling
> it.  Without the patch, I received these compile errors.
>
>      $ cc -c -I.. -I../src -I../gd1.3 -D_REENTRANT -D_GNU_SOURCE
>      -DTHREADS_HAVE_PIDS -DDEBIAN -fno-strict-aliasing -pipe
>      -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
>      -DHAVE_CONFIG_H -O2 -DVERSION=\"1.000503\"
>      -DXS_VERSION=\"1.000503\" -fPIC "-I/usr/lib/perl/5.8/CORE"
>      -DPERLPATCHLEVEL=8 RRDs.c
(Continue reading)

Permalink | Reply | 0 comments |

Gmane