public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] suricata: Perform ruleset update every 12 hours.
Date: Sun, 08 May 2022 17:12:33 +0100	[thread overview]
Message-ID: <1A6869C7-B4B3-4AF7-846E-FFA67AF78C95@ipfire.org> (raw)
In-Reply-To: <20220508132303.4175-1-stefan.schantl@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]

Hello Stefan,

What happens to firewalls that do not run 24/7?

Will this job be performed after 12 hours have passed no matter how long? So let’s say I shut down a system for a day, would the job run immediately?

-Michael

> On 8 May 2022, at 14:23, Stefan Schantl <stefan.schantl(a)ipfire.org> wrote:
> 
> Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
> ---
> config/cron/crontab | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/config/cron/crontab b/config/cron/crontab
> index d61d26619..c42104626 100644
> --- a/config/cron/crontab
> +++ b/config/cron/crontab
> @@ -62,8 +62,8 @@ HOME=/
> # Update location database
> %hourly,random * [ -f "/var/ipfire/red/active" ] && /usr/local/bin/update-location-database >/dev/null 2>&1
> 
> -# Update surciata rules.
> -%daily,random * [ -f "/var/ipfire/red/active" ] && /usr/local/bin/update-ids-ruleset >/dev/null 2>&1
> +# Perform a surciata rules update every 12 hours.
> +@ 12h [ -f "/var/ipfire/red/active" ] && /usr/local/bin/update-ids-ruleset >/dev/null 2>&1
> 
> # Retry sending spooled mails regularly
> %hourly * /usr/sbin/dma -q
> -- 
> 2.30.2
> 


  parent reply	other threads:[~2022-05-08 16:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-08 13:23 Stefan Schantl
2022-05-08 14:23 ` Peter Müller
2022-05-08 16:12 ` Michael Tremer [this message]
     [not found] <c2a2e4d8-4c28-0221-ceb7-155488738412@yahoo.com>
2022-05-12  9:23 ` : " Michael Tremer

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=1A6869C7-B4B3-4AF7-846E-FFA67AF78C95@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@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