Bug #1619
closed
crontab wrong expiretable check time
0%
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
- * * * * 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
Updated by Chris Buechler almost 14 years ago
- Status changed from New to Rejected
it's not designed to expire them after exactly an hour and has no need for doing so. Running it more frequently would be a waste of resources in most instances. You can edit your own entry if you prefer it to run every minute.
Updated by Marcello Silva Coutinho almost 14 years ago
Ir Does not make sense. Why configure an Option To expire in 60 minutes but not in 60 minutes.
If i want To limit connections per second in my box, all ips that reach this limit will be blocked for two hours on virus table, not limited.
How can i limit it instead of blocking 'for ever'?
I've never used advanced limit rules just because it was dropping instead of limiting.
May be someone else have same problem using advanced rules options.
May be someone else question too.