Per Jessen wrote: > I guess a temporary work-around for me would be to write the PNG output to a > file > instead of stdout - that way I still end up with a valid PNG file, even if > libart spews > out some warnings.
This isn't stricly rrd-related, but in this context, well - I call "rrdtool graph" as a system() call - stdout is redirected to an open HTTP connection, so I'm feeding the PNG directly to a browser. As the problem was that the PNG ended up being invalid because of the stderr warnings from libart, I figured I would just close stderr before I do the system() call. Which does partially work - except the browser ends up hanging and waiting for the last bit of the PNG. For instance the legends and the X-axis. I don't really understand this. I've tried 1) just closing stderr, 2) writing to /dev/null and 3) writing to a logfile. It's as if the connection is being properly closed - but it works fine when I don't fiddle with stderr. Any hints anyone? /Per Jessen, Zürich -- http://www.spamchek.ch/freetrial - managed anti-spam and anti-virus solution. Überzeugen Sie sich - 30 Tage kostenlos und unverbindlich! -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://lists.ee.ethz.ch/rrd-developers WebAdmin http://lists.ee.ethz.ch/lsg2.cgi
