Nigel Kukard wrote:
Quotas is implemented using a moving window, this window moves
automatically with time so there is no fixed counter of how much is used
or if the user is currently over quota.
On that note, I'm a bit puzzled
over the floating point number that shows the current number (the
"counter" parameter in the quotas_tracking table). Does, in fact, this
number somehow incorporate this information?
Well, yes.
You can check if the counter exceeds the limit for CumulativeSize and if
counter + 1 >= limit for MessageCount.
Counter is basically the extrapolated count either of cumulative size or
messages received in the time period. CumulativeSize will exceed the
counter, MessageCount won't.
Other than that, maybe the accounting module may be a better bet?
-N
Hmmm... seems like you'd have to run a comparison for every entry vs.
the policy number and the associated limit. I see what you mean about
the window; it's a very different implementation than in V1.8.X.
We're running 2.0.7, so it looks like we should take a closer look at
2.1.0 or higher to gain access to the accounting module; how stable is
it at this point?
Would the MySQL DB have to be re-created to support this, or is it just
a question up upgrading the software on the servers?
Thanks,
--Tobias
_______________________________________________
Users mailing list
[email protected]
http://lists.policyd.org/mailman/listinfo/users
