From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] log.dat: Fixes bug#12950 - adding apcupsd to system logs list
Date: Wed, 22 Feb 2023 09:52:17 +0000 [thread overview]
Message-ID: <269B858A-452B-41EA-BD7D-A1F009463CC5@ipfire.org> (raw)
In-Reply-To: <20230221135517.6286-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 21 Feb 2023, at 13:55, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> - Patch tested out on my production system that has apcupsd running on it. APCUPS was
> in the list of options in the system logs and entries from apcupsd were extracted
> correctly in the wui.
>
> Fixes: Bug#12950
> Tested-by: Adolf Belka <adolf.belka(a)ipfire.org>
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> html/cgi-bin/logs.cgi/log.dat | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/html/cgi-bin/logs.cgi/log.dat b/html/cgi-bin/logs.cgi/log.dat
> index 5fb1fcd5d..bf71b3c9f 100644
> --- a/html/cgi-bin/logs.cgi/log.dat
> +++ b/html/cgi-bin/logs.cgi/log.dat
> @@ -49,6 +49,7 @@ $cgiparams{'ACTION'} = '';
> $cgiparams{'SECTION'} = 'ipfire';
>
> my %sections = (
> + 'apcupsd' => '(apcupsd\[.*?\]: )',
> 'auth' => '(\w+\(pam_unix\)\[.*\]: )',
> 'wio' => '(wio:|wio\[.*\])',
> 'captive' => '(Captive:)',
> @@ -81,6 +82,7 @@ my %sections = (
>
> # Translations for the %sections array.
> my %trsections = (
> + 'apcupsd' => 'APCUPS',
> 'auth' => "$Lang::tr{'loginlogout'}",
> 'wio' => 'Who Is Online?',
> 'captive' => $Lang::tr{'Captive'},
> --
> 2.39.2
>
prev parent reply other threads:[~2023-02-22 9:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 13:55 Adolf Belka
2023-02-22 9:52 ` Michael Tremer [this message]
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=269B858A-452B-41EA-BD7D-A1F009463CC5@ipfire.org \
--to=michael.tremer@ipfire.org \
--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