Mysterious quota poltergeist

[GreenGecko]

Yup, tried to do that. Works for a little while, depending on how actively
one is hitting the mailbox, but the problem crops up again. That fix could
last for as little as a few minutes. If you shut down your mail client it
will last until you run the mail client again, so it has something to do
with the user logging in.

--Marie

On 2/22/06, Scott Russell <lnxgeek at us.ibm.com> wrote:
>
> GreenGecko wrote:
> > It doesn't work to set it to no quotas. The numbers get reset anyway.
> > That was how we had it set up originally. Attempts to set the quota to
> > someething high was what we were trying as an altenative to no quotas
> > because it gave us something to try.  No matter the setting we give
> > it, it keeps reseting itself to this bizarre number and throwing the
> > quota errors.  Even with the quota files locked it still would report
> > this bogus number. Now we have it in the database still with no joy.
>
> Without actually solving the mystery, just remove the quotadb file of
> the affected user then run quota -f user.acct to fix up the quota for
> the account.
>
> --
> Scott Russell <lnxgeek at us.ibm.com>
> IBM Linux Technology Center
>
>


--
-------------------------------------------------------------
Marie Williams * darkirony.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.andrew.cmu.edu/mailman/private/info-cyrus/attachments/20060225/0b9e0452/attachment.html