From: "Peter Müller" <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. a924020ea83bad4802ff59dbbcb3bb7d32b29cc2
Date: Thu, 23 Jun 2022 07:28:48 +0000 [thread overview]
Message-ID: <4LTBh03Ykhz2y8j@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1531 bytes --]
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 a924020ea83bad4802ff59dbbcb3bb7d32b29cc2 (commit)
from d9aece2af988012a16a7f446e6f65f4d112744df (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 a924020ea83bad4802ff59dbbcb3bb7d32b29cc2
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Thu Jun 23 07:27:19 2022 +0000
Core Update 169: Restart ntpd to apply configuration changes
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/169/update.sh | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/config/rootfiles/core/169/update.sh b/config/rootfiles/core/169/update.sh
index a27f20a30..abca6c336 100644
--- a/config/rootfiles/core/169/update.sh
+++ b/config/rootfiles/core/169/update.sh
@@ -150,6 +150,7 @@ ldconfig
# Start services
telinit u
/etc/init.d/firewall restart
+/etc/init.d/ntp restart
/etc/init.d/apache start
/etc/init.d/unbound start
/etc/init.d/squid start
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-06-23 7:28 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=4LTBh03Ykhz2y8j@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