public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] update-ipblocklists: remove "<INFO> Skipping" log entries
Date: Wed, 05 Jun 2024 10:28:13 +0100	[thread overview]
Message-ID: <CD9A7252-72E1-4F4E-B1EB-FECE59C0F7E5@ipfire.org> (raw)
In-Reply-To: <20240604202253.3546966-1-jon.murphy@ipfire.org>

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

Hello Jon,

Why should this not be logged?

-Michael

> On 4 Jun 2024, at 21:22, Jon Murphy <jon.murphy(a)ipfire.org> wrote:
> 
> - Remove two <INFO> log entries from message log.
> 
> Signed-off-by: Jon Murphy <jon.murphy(a)ipfire.org>
> ---
> src/scripts/update-ipblocklists | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/src/scripts/update-ipblocklists b/src/scripts/update-ipblocklists
> index a17b47999..dddde8d27 100644
> --- a/src/scripts/update-ipblocklists
> +++ b/src/scripts/update-ipblocklists
> @@ -86,7 +86,7 @@ foreach my $blocklist (@blocklists) {
> # Check if enough time has passed since the last download of the list.
> if ($time <= $holdoff_time) {
> # To frequent updates, log to syslog.
> - &_log_to_syslog("<INFO> Skipping $blocklist blocklist - Too frequent update attempts!");
> + # &_log_to_syslog("<INFO> Skipping $blocklist blocklist - Too frequent update attempts!");
> 
> # Skip this provider.
> next;
> @@ -100,7 +100,7 @@ foreach my $blocklist (@blocklists) {
> # Handle different return codes.
> if ($return eq "not_modified") {
> # Log notice to syslog.
> - &_log_to_syslog("<INFO> Skipping $blocklist blocklist - It has not been modified!");
> + # &_log_to_syslog("<INFO> Skipping $blocklist blocklist - It has not been modified!");
> } elsif ($return eq "dl_error") {
> # Log error to the syslog.
> &_log_to_syslog("<ERROR> Could not update $blocklist blocklist - Download error\!");
> -- 
> 2.30.2
> 


  reply	other threads:[~2024-06-05  9:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04 20:22 Jon Murphy
2024-06-05  9:28 ` Michael Tremer [this message]
2024-06-05  9:55   ` Adolf Belka
     [not found] <A472F1A4-A3AB-4E37-9445-4517A3C87C12@ipfire.org>
2024-06-06 14:55 ` Adolf Belka
     [not found] <EFBA494A-FB26-4FA6-87E1-0BE7A3CA154B@ipfire.org>
2024-06-07  7:40 ` Adolf Belka
     [not found] <9E099FC3-0DD0-4FDC-94D4-3E44CB093DC0@ipfire.org>
2024-06-07 10:40 ` Michael Tremer
     [not found] <AAFFDC1D-9A3C-4CB3-8782-E4E608E0074B@ipfire.org>
2024-06-24 15:21 ` Adolf Belka

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=CD9A7252-72E1-4F4E-B1EB-FECE59C0F7E5@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