Project

General

Profile

Actions

Bug #1619

closed

crontab wrong expiretable check time

Added by Marcello Silva Coutinho almost 14 years ago. Updated over 9 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Rules / NAT
Target version:
-
Start date:
06/24/2011
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:

Description

*/60 * * * * root /usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600 sshlockout

*/60 checks every 60 minutes if the time of that rule has expired.
if i have 59 minutes blocked when cron runs, it will take another 60 minutes to next check.
total time blocked 119 minutes

changing the rule to every minute(or every 3 minutes on large systems)
  • * * * * root /usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600 sshlockout*
    cron will reache blocked rule on time "-t 3600" and will unlock blocked ip.

same for
*/60 * * * * root /usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600 virusprot

Actions

Also available in: Atom PDF