From: Bernhard Bitsch <Bernhard.Bitsch@gmx.de>
To: development@lists.ipfire.org
Subject: Aw: Re: [PATCH 1/3] rrdimage: Add scripts for new graph display method
Date: Thu, 01 Apr 2021 15:58:15 +0200 [thread overview]
Message-ID: <trinity-7f4209da-c664-46db-b4f8-23d695f26400-1617285495550@3c-app-gmx-bap09> (raw)
In-Reply-To: <bec50845-bdf5-55d3-aa62-f86410e4b77a@leo-andres.de>
[-- Attachment #1: Type: text/plain, Size: 1561 bytes --]
Hi,
I didn't look at your patch in depth 'til now. But the integration of the errors from RRDtool looks good. Thanks for taking my suggestion in the discussion. I wasn't able to look at this since then, but it seems to be my solution I've tried some time ago on my system.
Could you test it with some errors of rrdgraph()?
Regards,
Bernhard
> Gesendet: Donnerstag, 01. April 2021 um 15:36 Uhr
> Von: "Leo Hofmann" <hofmann(a)leo-andres.de>
> An: development(a)lists.ipfire.org
> Betreff: Re: [PATCH 1/3] rrdimage: Add scripts for new graph display method
>
> Hi all,
>
> this series of patches is a follow-up to this discussion: https://lists.ipfire.org/pipermail/development/2021-March/009523.html
>
> I decided to write a new CGI which handles the graph image generation (png). This allowed me to add new features and remove a lot of uneccessary parameter handling from the other CGIs.
> I think this is in presentable form now. But there are still some issues I'd like to hear your opinion on:
>
> - Because I have collected all the graph functions from the CGIs, there is now a very long if-elseif chain in getrrdimage.cgi. I tried my best to keep this as readable as possible. But I'd be happy to rewrite that if someone knows a better method.
>
> - My test system doesn't have any hardware sensors or IPsec connections. I'm pretty sure that these graphs work but I can't test them.
>
> - getrrdimage.cgi redirects graphs it can't generate to ensure compatibility with addons. Is that necessary?
>
> Happy holidays!
> Leo
>
next prev parent reply other threads:[~2021-04-01 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 13:35 Leo-Andres Hofmann
2021-04-01 13:35 ` [PATCH 2/3] rrdimage: Add CSS and Javascript to ipfire theme Leo-Andres Hofmann
2021-04-01 13:35 ` [PATCH 3/3] rrdimage: Switch graphs.pl to the new graph scripts Leo-Andres Hofmann
2021-04-01 13:36 ` [PATCH 1/3] rrdimage: Add scripts for new graph display method Leo Hofmann
2021-04-01 13:58 ` Bernhard Bitsch [this message]
[not found] <7f0b70ed-b52f-aeb6-048d-580a696d7993@leo-andres.de>
2021-04-01 15:09 ` Aw: " Bernhard Bitsch
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-7f4209da-c664-46db-b4f8-23d695f26400-1617285495550@3c-app-gmx-bap09 \
--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