On Tue, 31 Aug 2004, Ken Murchison wrote:
This is a 64 bit platform, I wonder if for some reason it's broken in that
case. Though... I don't see it.
Right. I *believe* the changes in question are those between 2.2.1 and 2.2.3
(caching additional headers and making a hole for 64-bit quotas), but
Derrick J Brashear wrote:
On Tue, 31 Aug 2004, Ken Murchison wrote:
It sounds like the on-the-fly upgrade of cyrus.index and cyrus.cache
is broken when going to 2.2.1 to 2.2.8. I've looked at the code and
nothing seems obvious (yet), so if you can duplicate it and possibly
post before and after
On Tue, 31 Aug 2004, Ken Murchison wrote:
It sounds like the on-the-fly upgrade of cyrus.index and cyrus.cache is
broken when going to 2.2.1 to 2.2.8. I've looked at the code and nothing
seems obvious (yet), so if you can duplicate it and possibly post before and
after versions of these files,
Scott Adkins wrote:
Okay, so I have just attempted for a second time to upgrade our Cyrus
server
on the production box from version 2.2.1 to version 2.2.8. The upgrade was
a failure and I had to back out and go through a not-quite-painless
recovery
process on the user accounts affected by the up
Okay, so I have just attempted for a second time to upgrade our Cyrus server
on the production box from version 2.2.1 to version 2.2.8. The upgrade was
a failure and I had to back out and go through a not-quite-painless recovery
process on the user accounts affected by the upgrade.
So, the first t