On Wed, 20 Feb 2008, Mark Crispin wrote:
I guess the implementation would mean another .mixsomething meta file. In
that case, it would be nice to have a mix tools to rebuild this file.
In the case of the .mixsortcache file, the rebuild procedure is simply to
delete it. I probably would do the same thing with the new cache. Is there
a reason why this isn't good enough?
No.
This was a general comment, based on the fact that the rebuild tools
weren't available at the beginning of the mix era when they were needed
the most. So if some meta file can't be recreated automatically, the
tool should be available from the beginning.
imapd already does a lot of error recovery and correction in cases where it
perceives that it can remediate the problem without data loss. I will
continue to add more of these over time.
Deleting corrupt cache files would be a good candidate.
On the other hand, I can't remember when I last needed to rebuild something,
so this is probably not an important issue.
That's how I hope that most people will feel!
It's probably only us who are foolish enough to run development versions
in production who run into these kind of bugs. Normally I'm not that
bold, but the mix format was too tempting.
/Per
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
