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. b994319910d3c908be8a0a4e2ef48bf39c7f97eb
Date: Mon, 01 Jun 2026 13:44:26 +0000 (UTC)	[thread overview]
Message-ID: <4gTZvG4ytvz2xK2@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  b994319910d3c908be8a0a4e2ef48bf39c7f97eb (commit)
      from  1dbea98bc14984d847fa932453ff2059c6e47be7 (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 b994319910d3c908be8a0a4e2ef48bf39c7f97eb
Author: Michael Tremer <michael.tremer@ipfire.org>
Date:   Mon Jun 1 13:16:30 2026 +0000

    cron: Update RPZs once an hour
    
    Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>

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

Summary of changes:
 config/cron/crontab | 3 +++
 1 file changed, 3 insertions(+)

Difference in files:
diff --git a/config/cron/crontab b/config/cron/crontab
index df326977d..5945e20e9 100644
--- a/config/cron/crontab
+++ b/config/cron/crontab
@@ -87,3 +87,6 @@ HOME=/
 
 # Cleanup the collectd RRD (graphs)
 %weekly * * /bin/find /var/log/rrd -mtime +365 -type f -name '*.rrd' -delete -o -type d -empty -delete
+
+# Update RPZs
+%hourly,random *	/usr/local/bin/update-rpzs


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


                 reply	other threads:[~2026-06-01 13:44 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=4gTZvG4ytvz2xK2@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