Project

General

Profile

Actions
Copy link

Bug #11636

closed

Unused Limiter entries with schedules create unnecessary cron jobs

Added by Viktor Gurov over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Viktor Gurov
Category:
Traffic Shaper (Limiters)
Target version:
2.5.2
Start date:
03/08/2021
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
21.05
Release Notes:
Default
Affected Version:
2.5.0
Affected Architecture:

Description

If you create a Limiter with a schedule but do not apply it to any firewall rules,
it will create a cron job: "0,15,30,45 * * * * root /etc/rc.filter_configure_sync" which causes latency spikes.

Actions
Copy link
 #2

Updated by Jim Pingle over 3 years ago

  • Status changed from New to Pull Request Review
Actions
Copy link
 #3

Updated by Jim Pingle over 3 years ago

  • Target version set to CE-Next
Actions
Copy link
 #4

Updated by Renato Botelho over 3 years ago

  • Status changed from Pull Request Review to Feedback
  • Assignee set to Viktor Gurov

PR has been merged. Thanks!

Actions
Copy link
 #5

Updated by Renato Botelho over 3 years ago

  • Target version changed from CE-Next to 2.6.0
Actions
Copy link
 #6

Updated by Viktor Gurov over 3 years ago

  • % Done changed from 0 to 100
Actions
Copy link
 #7

Updated by Jim Pingle over 3 years ago

  • Plus Target Version set to 21.05
Actions
Copy link
 #8

Updated by Jim Pingle over 3 years ago

Already in 21.05 branch.

Actions
Copy link
 #9

Updated by Jim Pingle over 3 years ago

  • Subject changed from Unused Limiters with a schedule creates cron job to Unused Limiter entries with schedules create unnecessary cron jobs

Updating subject for release notes.

Actions
Copy link
 #10

Updated by Jim Pingle over 3 years ago

  • Target version changed from 2.6.0 to 2.5.2
Actions
Copy link
 #11

Updated by Marcos M over 3 years ago

  • Status changed from Feedback to Resolved

Tested and working on 21.05/2.5.2. Cron job was not added until a rule contained the limiter, and the cron job was removed after the rule was removed.

Marking as resolved.

Actions
Copy link

Also available in: Atom PDF