From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: ipblocklist - ipblocklist.cgi page shows Error
Date: Mon, 02 May 2022 20:59:50 +0200 [thread overview]
Message-ID: <f56e5890bc5d7a257397f60b103db94a497dc74c.camel@ipfire.org> (raw)
In-Reply-To: <10d2e654-9a0e-8795-bf36-25ccce34539d@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 765 bytes --]
Hello Charles,
no they didn't get lost, simply there have been changed so much in the
output. So the old file for logwatch would not work anymore and I'm not
familiar with this software.
Shame on me, I forgot to point to this - so please if there is
somewhere, which could get this to work again, help is very
appreciated.
Thanks in advance,
-Stefan
> Hi Stefan,
> In case this item got lost in some of the other chatter on the list
>
> > This is a minor nit on the ipblocklist.cgi page. Changing any
> > setting generates the notice to reload the FW ruleset -- showing
> > the words, "Error messages" at the top. It would be nice to have
> > this show the notice -- like the Location Block page -- rather than
> > indicating Error
> -Charles
>
>
parent reply other threads:[~2022-05-02 18:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <10d2e654-9a0e-8795-bf36-25ccce34539d@yahoo.com>]
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=f56e5890bc5d7a257397f60b103db94a497dc74c.camel@ipfire.org \
--to=stefan.schantl@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