public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 2/2] exclude: Remove the urlfilter pl programs from a backup
Date: Sat, 01 Mar 2025 13:46:02 +0100	[thread overview]
Message-ID: <20250301124602.5489-2-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20250301124602.5489-1-adolf.belka@ipfire.org>

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

- When dealing with the qos bug fix for backing up .pl programs I also then searched all
   the /var/ipfire directory tree looking for any other .pl files that were being backed
   up and found that there were two for the urlfilter.
- This patch adds the .pl files in the urlfilter/bin directory to the exclude list.
- In the same way as for the qos change the exclude addition also means that these files
   will not be restorewd from any earlier backup.
- Also tested and confirmed on a physical IPFire system.

Tested-by: Adolf Belka <adolf.belka(a)ipfire.org>
Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
 config/backup/exclude | 1 +
 1 file changed, 1 insertion(+)

diff --git a/config/backup/exclude b/config/backup/exclude
index fb6477d26..a69eed767 100644
--- a/config/backup/exclude
+++ b/config/backup/exclude
@@ -9,3 +9,4 @@ var/ipfire/qos/bin/*.pl
 var/ipfire/suricata/oinkmaster.conf
 var/ipfire/suricata/ruleset-sources
 var/ipfire/urlfilter/blacklists/*/*.db
+var/ipfire/urlfilter/bin/*.pl
-- 
2.48.1


      reply	other threads:[~2025-03-01 12:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-01 12:46 [PATCH 1/2] exclude: Fix bug13736 - stop backup of qos perl programs Adolf Belka
2025-03-01 12:46 ` Adolf Belka [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=20250301124602.5489-2-adolf.belka@ipfire.org \
    --to=adolf.belka@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