Tobias,
I'm running 1.81 - I can see my _quota_{cur,max} are unsigned int's ? which
afaik is 4gig not 2gig?
Also - checking mysql site, there is 8byte BIGINT which is
18446744073709551615 what are the options for changing this in the policyd
db - or is it set in code also?
Jon
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tobias
Kreidl
Sent: 26 October 2007 16:53
To: [email protected]
Subject: [policyd-users] unlimited sender quota
Jon,
The MySQL DB has various quota varibled defined as INTEGER (not sure why
not UNSIGNED INTEGER), and this limits the maximum value to
2,147,438,647. I do not think MySQL suports any larger integer values.
Oracle, on the other hand, supports both Int64 and UInt64 integers.
In your case, you'd have to set a shorter time interval, if this is an
issue. Or, as I proposed, it'd be nice to disable monitoring of sender
quotas altogether -- maybe setting the value negative could trigger not
the setting of the default value, but not tracking quotas at all - that
way, the accumulated totals could be left at zero and there would never
be an overflow problem.
--Tobias
Jon Duggan wrote:
> I have a question regarding this sender quota also. What's the reason
> behind the 2gb limit?
>
> I was hoping to use the sender quota on a per month basis but 2gb/month
for
> some clients is simply not enough - meaning our power users are having to
> use a different system - wasting a whole machine.
>
> Are there any plans to increase the 2gb limit or is there a (near) trivial
> way to increase it?
>
>
> jduggan
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Tobias
J.
> Kreidl
> Sent: 26 October 2007 05:36
> To: [email protected]
> Subject: [policyd-users] unlimited sender quota
>
> I read in an archived posting (2006?) that there was supposed to be a
> change that if the maximum sender quota (which defaults to 250 MB) is set
> to zero, that it would be interpreted as there being no limit in a future
> release of policyd, instead of being set to the default value. I tried
> this recently in policyd 1.82 and it still reverted to the default of
> 250 MB for the specified time interval.
>
> For now, I've increased it to near the max. of 2.1 GB, which I think will
> be safe, but what I wanted to ask is whether or not this was still planned
> as a change or did I miss somewhere that this planned change was
> retracted?
>
> --Tobias
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
policyd-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/policyd-users
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
policyd-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/policyd-users
