Hey Daniel,
Friday, July 27, 2001, 4:46:25 AM, you wrote:
DMsc> Hi Kevin,
DMsc> reading the quotas from LDAP is a good idea. The problem
DMsc> is updating the used disc space somewhere. If you want to
DMsc> store this information also on LDAP, it will need an update
DMsc> for every incoming message. This is very problematic,
DMsc> because usually, LDAP servers are not optimized for doing
DMsc> updates. 1 or 2 updates pre seconds should not be a problem,
DMsc> but many updates per second will stress your LDAP server.
DMsc> This will not scale very well, it will be more complex if
DMsc> you use replication.
DMsc> Does it make sense to you to store the quota on LDAP and the
DMsc> used disc space on a local file ? For me this doesn't seem
DMsc> to be a good solution, because you have the data on 2 places.
Well, this seems to make sense to me. Perhaps someone else could provide
some insight though. Rationale: I want a central location for all
information, so I change user data in one spot. I'm already using LDAP as a
means of authentication and I use it for mail routing with postfix. I would
like to be able to set quotas in LDAP so that I have a nice easy location
for this. If the user needs more space, I just change an entry in LDAP.
And I can do a simple LDAP search to always see what the user has for
maximum space.
Now, I really don't care how much space the user uses up, so long as it's
below that quota. That is of concern only to cyrus and the user in
question. So, I see no need for this to be stored in LDAP. Yes, it would
be kinda nifty to do an ldapsearch and say "hey you have 3 megs left", but
in reality, like you said, to maintain it in LDAP is more trouble than its
worth, and that information is really of no consequence to me :)
--
Kevin
