public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. f5fc7a85e5aba4b12feeccb56aad994e350d174d
Date: Mon, 10 Aug 2026 08:35:20 +0000 (UTC)	[thread overview]
Message-ID: <4hJSkJ0ldPz2y5t@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, next has been updated
       via  f5fc7a85e5aba4b12feeccb56aad994e350d174d (commit)
      from  c872f86c6f9bb7db7744503e1185e313701070d0 (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 f5fc7a85e5aba4b12feeccb56aad994e350d174d
Author: Michael Tremer <michael.tremer@ipfire.org>
Date:   Mon Aug 10 08:35:08 2026 +0000

    core205: Restart OpenVPN
    
    Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 config/rootfiles/core/205/update.sh | 2 ++
 1 file changed, 2 insertions(+)

Difference in files:
diff --git a/config/rootfiles/core/205/update.sh b/config/rootfiles/core/205/update.sh
index 8b9d9d8f2..bf0376020 100644
--- a/config/rootfiles/core/205/update.sh
+++ b/config/rootfiles/core/205/update.sh
@@ -60,6 +60,8 @@ gpgconf --kill all
 
 # Start services
 /etc/init.d/knot-resolver restart
+/etc/init.d/openvpn-rw restart
+/etc/init.d/openvpn-n2n restart
 
 # This update needs a reboot...
 touch /var/run/need_reboot


hooks/post-receive
--
IPFire 2.x development tree


                 reply	other threads:[~2026-08-10  8:35 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=4hJSkJ0ldPz2y5t@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