From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core188, updated. 699124028a4a08c9b07de9348df37fa2950afe15
Date: Fri, 20 Sep 2024 10:20:19 +0000 [thread overview]
Message-ID: <4X97gR5WMWz2xn5@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1651 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, core188 has been updated
via 699124028a4a08c9b07de9348df37fa2950afe15 (commit)
from 0694e7e45fa1a8d44df63b7c4c984b8b7cca2aec (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 699124028a4a08c9b07de9348df37fa2950afe15
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Sep 20 10:19:57 2024 +0000
core188: Regenerate Suricata rulefiles
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/188/update.sh | 4 ++++
1 file changed, 4 insertions(+)
Difference in files:
diff --git a/config/rootfiles/core/188/update.sh b/config/rootfiles/core/188/update.sh
index 276223052..facaeede8 100644
--- a/config/rootfiles/core/188/update.sh
+++ b/config/rootfiles/core/188/update.sh
@@ -121,6 +121,10 @@ ldconfig
/etc/init.d/apache restart
/etc/init.d/unbound restart
+# Regenerate Suricata rule files
+perl -e "require '/var/ipfire/ids-functions.pl'; &IDS::write_used_rulefiles_file();"t
+/etc/init.d/suricata reload
+
# Build initial ramdisks
dracut --regenerate-all --force
KVER="xxxKVERxxx"
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2024-09-20 10:20 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=4X97gR5WMWz2xn5@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