You could set the cleanup to 60 days (so it won't delete anything) and then create your own cron entry of something like this...
1 1 1 * * echo "truncate throttle;" | mysql -u postfix -pp0stf1x policyd eg: at 1minute past 1am on the 1st of the month truncate the throttle table. dave PS: I didn't test this, just thinking out loud. ----- Original Message ----- From: "Jon Duggan" <[EMAIL PROTECTED]> To: <policyd-users@lists.sourceforge.net> Sent: Tuesday, April 24, 2007 6:09 PM Subject: Re: [policyd-users] _time_limit in throttle table Hi, Yes i realise it's quite petty, but as has been pointed out to me by the management that be, some months have 28 days (even 29 on a leap year :) ), some 30, some 31 so they'd like a *true* month by month account of quota's. I'm not sure i understand the SENDER_INACTIVE_EXPIRE= feature? Does this overrule the _time_limit entry or something? As i say, we want to enforce xGB(_quota_max)/month where the month is a true month by month account rather than a fixed '30' day period etc ...Guess this is way off the scope of policyd without some hacking ----------------------8<----------------------- ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ policyd-users mailing list policyd-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/policyd-users
