From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 30ccb9ed80ee3ad70403794da4c937fd183b9bd8
Date: Tue, 21 Apr 2026 09:32:58 +0000 (UTC) [thread overview]
Message-ID: <4g0HG22HQRz2xTH@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 30ccb9ed80ee3ad70403794da4c937fd183b9bd8 (commit)
from 818a2094757986540f3366c79f46e1409b2b4151 (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 30ccb9ed80ee3ad70403794da4c937fd183b9bd8
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Tue Apr 21 09:32:11 2026 +0000
logrotate: Rotate Suricata logs daily
This patch also cleans up what happens. Logrotate will automatically
delete any old log files and does not require any extra commands.
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/etc/logrotate.conf | 8 +++-----
config/rootfiles/core/202/filelists/files | 1 +
2 files changed, 4 insertions(+), 5 deletions(-)
Difference in files:
diff --git a/config/etc/logrotate.conf b/config/etc/logrotate.conf
index c5f9883c7..2f79de933 100644
--- a/config/etc/logrotate.conf
+++ b/config/etc/logrotate.conf
@@ -29,14 +29,12 @@ include /etc/logrotate.d
}
/var/log/suricata/*.log {
- weekly
+ daily
copytruncate
- compress
- ifempty
+ notifempty
missingok
+ sharedscripts
postrotate
- /bin/find /var/log/suricata -path '/var/log/suricata/[0-9]*' -prune -exec /bin/rm -rf {} \;
- /bin/find /var/log/suricata -name 'fast.log.*' -mtime +28 -exec /bin/rm -rf {} \;
/bin/kill -HUP `cat /var/run/suricata.pid 2> /dev/null` 2> /dev/null || true
endscript
}
diff --git a/config/rootfiles/core/202/filelists/files b/config/rootfiles/core/202/filelists/files
index ebaef1717..50fe9d2c2 100644
--- a/config/rootfiles/core/202/filelists/files
+++ b/config/rootfiles/core/202/filelists/files
@@ -1,3 +1,4 @@
+etc/logrotate.conf
etc/rc.d/init.d/firewall
etc/rc.d/init.d/sysklogd
etc/rc.d/init.d/unbound
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2026-04-21 9:32 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=4g0HG22HQRz2xTH@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