[Kolab-devel] when quota checking is done on kolabd?
Martin Konold
martin.konold at erfrakon.de
Fri Mar 31 23:20:26 CEST 2006
Am Donnerstag, 30. März 2006 12:01 schrieb Fabio Pietrosanti:
> stop creating mailbox until it stop the quota set/reset of all users.
imho it is a broken implementation(*) of kolabd to fiddle with the quota
setting of every user even though 99.999 percent of the quota settings did
not change.
> How it's possible to schedule a quota set/reset periodically (monthly?) ?
This would be a fast solution but in the mid-term it compicates matters and
decreases the usability. (People expect that quota changes take effect
immediately not somewhen later during the month)
Regards,
-- martin
(*) I see two potential solutions: Either let the kolabd cache the quota
information and then do a simple comparison between the cache and the LDAP
information (should take less than 60 s for 80 thousand users) or even better
make kolabd smarter to understand changes in LDAP and only set quota for
accounts which acually got modified. The later is my prefered approach as it
allows for better scalability.
--
http://www.erfrakon.com/
Erlewein, Frank, Konold & Partner - Beratende Ingenieure und Physiker
More information about the devel
mailing list