|
Notes |
|
|
(0002820)
|
|
fgaudreault
|
2012-06-22 17:50
(edited on: 2012-06-22 17:53) |
|
Branched in feature/acct_violations
I went even further:
- Added a fast close/open button:
* Closing using that button will put NOW as the release_date
* Opening using that button will remove the release_date (and open the violation). We can see if we want to put the new release_date then (if we open a violation with a window).
- Added a "window" concept to the violations (just like unregdate)
* You can define a period of time you want the violation to be active
* Past that time, the violation will be closed by pfmon automatically
* Supports the normalized format + "dynamic" keyword (see below). "0" is considered forever.
TO DO:
- Support the dynamic keyword (for accounting violations). The core will calculate the appropriate window.
* Exemple: I have an accounting violation of 20G/month, I want to put the release date at the end of the month if you trigger the limit after say 3days.
|
|
|
|
(0002845)
|
|
fgaudreault
|
|
2012-07-19 11:08
|
|
|
Ready in acct_violations. Missing the doc updates tho. |
|
|
|
(0002869)
|
|
fgaudreault
|
|
2012-08-03 17:10
|
|
|
|
|
|
|
fix released in 3.5.1 yesterday |
|