From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 27ec6f7860da27d046ddeb33809eba897b0766e7
Date: Sun, 1 Jun 2025 15:02:13 +0000 (UTC) [thread overview]
Message-ID: <4b9KvT3Pjjz2xhX@people01.haj.ipfire.org> (raw)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, master has been updated
via 27ec6f7860da27d046ddeb33809eba897b0766e7 (commit)
from 9ef726eeb272104656baf3c38eca75c4dc5bea10 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 27ec6f7860da27d046ddeb33809eba897b0766e7
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Sun Jun 1 17:00:51 2025 +0200
wireguard: Don't try to delete any interfaces that don't exist
When the WireGuard interfaces are being destroyed, we are using some
globbing to identify the right interfaces. If there are no interfaces
the globbing string does not match anything and is returned itself. To
avoid an error when trying to delete an interface that never existed, we
configure the shell to never expand empty globbings.
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
src/initscripts/system/wireguard | 2 ++
1 file changed, 2 insertions(+)
Difference in files:
diff --git a/src/initscripts/system/wireguard b/src/initscripts/system/wireguard
index 7decce223..00862743b 100644
--- a/src/initscripts/system/wireguard
+++ b/src/initscripts/system/wireguard
@@ -19,6 +19,8 @@
# #
###############################################################################
+shopt -s nullglob
+
. /etc/sysconfig/rc
. ${rc_functions}
. /etc/rc.d/init.d/networking/functions.network
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2025-06-01 15:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4b9KvT3Pjjz2xhX@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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