public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Bernhard Bitsch <Bernhard.Bitsch@gmx.de>
To: development@lists.ipfire.org
Subject: Aw: Re: 'rrdtool 1.5.3' - errors in specific graphs - update
Date: Sun, 17 May 2015 15:06:19 +0200	[thread overview]
Message-ID: <trinity-c7bd0ad1-332f-4ecc-9532-5b00321c48b0-1431867978994@3capp-gmx-bs18> (raw)

[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]

Hi,

I added a comment about the errors to Bugzilla.

Besides this specific errors, this remembered me to a general issue with the graphics. 
The structure is inherited from the way graphing was/is done in Smoothwall/IPCop: The graphics are generated periodically and saved to files. The WUI just displays these graphic files. Errors in generation are printed to stdout.
IPFire generates the graphics on-the-fly ( graphics data are output to stdout and thus embedded directly into the HTML code ). An error output to stdout gives an invalid graphic element. 
Therefore we should redesign the interface to these graphing functions allowing a return of errors.
I once have found a solution ( I think in assisting in development of OVPN graphs ), but don't remember it in the moment. 

UPDATE to my former post:
I've found the changed files. The 'print' ( to stdout ) is simply changed to a call of General::log. The lines read now:

&General::log("Error in RRD::graph for .....: ".$ERROR)if $ERROR


Bernhard

                 reply	other threads:[~2015-05-17 13:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=trinity-c7bd0ad1-332f-4ecc-9532-5b00321c48b0-1431867978994@3capp-gmx-bs18 \
    --to=bernhard.bitsch@gmx.de \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox