>> I'm asking if anyone has written a reporting tool that can extract at >> least what instances are over quota at a given moment. If nothing like >> this exists, I'd like to ask the authors to at least consider storing >> this information in the table so that an easy comparison can be made >> to see if the user or machine is over the limit. When the time >> limit has expired, the counter could be zeroed out. >> >> > I find it very inconvenient that there is no way to easily make a simple > query > to the DB to see who's over quota. Is there some trick that I'm missing, or > would it be possible to include some information in the DB that reflects > if an instance is over quota or have a running count of the attempted > connections vs. the current connections?
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
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
