-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
that worked
but you need to be logged in as cyrus
(actually holds true for all the cyrus related apps.
i.e.:sync_client, etc)
>
> Maybe try 'man 8 quota'.
>
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mo
> On Fri, 15 Dec 2006, stas khromoy wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> andrew
>>
>> are you sure about quota -f ?
>> i don't believe there is one
>>
>> and looking at the man page for quota
>> i don't see it either
>> it has only -q -l -g -v -u as switches
>
> You ar
On Fri, 15 Dec 2006, stas khromoy wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
andrew
are you sure about quota -f ?
i don't believe there is one
and looking at the man page for quota
i don't see it either
it has only -q -l -g -v -u as switches
You are looking at the manpage for the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
andrew
are you sure about quota -f ?
i don't believe there is one
and looking at the man page for quota
i don't see it either
it has only -q -l -g -v -u as switches
thanks
Andrew Morgan wrote:
> On Fri, 15 Dec 2006, stas khromoy wrote:
>
>> -
On Fri, 15 Dec 2006, stas khromoy wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i've tried -f option as well
and it came up with the same result
i've monitored both /var/log/imapd.log and /var/log/messages
for errors during reconstruction ..i did not see anything
searched for imap_ioer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i've tried -f option as well
and it came up with the same result
i've monitored both /var/log/imapd.log and /var/log/messages
for errors during reconstruction ..i did not see anything
searched for imap_ioerror string as well in the above logs with no
reconstruct -r just reads the DB, so yes the DB must be out of sync
with the filesystem (not really "corruption" per se). reconstruct -r
-f reads the DB *and* the filesystem, but would still probably be
subject to the DB problem you're experiencing. When reconstruct
finds mailboxes in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
the folders were not there to begin with
they were removed a while ago
but when i run reconstruct
they are being detected.
could the db be corrupt ?
or maybe the cyrus.header files still has them indexed some how ?
the only thing i can think off to
Just to be clear, the problem is that reconstruct inappropriately
deleted folders after an error? Or, reconstruct is giving errors for
folders that were deleted (by the user) so you feel the errors are
inappropriate?
:wes
On 15 Dec 2006, at 09:14, stas khromoy wrote:
while working on rep
