Jeremy Howard wrote:
Tonight I am upgrading 4 mail servers currently running Cyrus 2016
release versions to cyrus-2-1-sasl-v1-tail from cvs
I am hoping this will correct allot of locking problems on the server
and add most of the bug fixes from 2016 (which is from June of 01
Ken Murchison wrote:
Jeremy Howard wrote:
...
To correct locking problems you may want to grab the skiplist backend
from
the current CVS, and use that with 2.0.16. CMU are now using this
backend in
production.
This won't work out of the box, because the cyrusdb interface has
changed
Jeremy Howard wrote:
Ken Murchison wrote:
Jeremy Howard wrote:
To correct locking problems you may want to grab the skiplist backend
from
the current CVS, and use that with 2016 CMU are now using this
backend in
production
This won't work out of the box, because the
Greetings,
Tonight I am upgrading 4 mail servers currently running Cyrus 2016
release versions to cyrus-2-1-sasl-v1-tail from cvs
Does anyone know of any problems i *may* run into with this particular
cvs version
Is it safe to assume this is stable 210 code designed to work with
sasl 1527
Tonight I am upgrading 4 mail servers currently running Cyrus 2.0.16
release versions to cyrus-2-1-sasl-v1-tail from cvs.
...
I am hoping this will correct allot of locking problems on the server
and add most of the bug fixes from 2.0.16 (which is from June of 01)
To correct locking
versions to cyrus-2-1-sasl-v1-tail from cvs
I am hoping this will correct allot of locking problems on the server
and add most of the bug fixes from 2016 (which is from June of 01)
To correct locking problems you may want to grab the skiplist backend from
the current CVS, and use
I had to back out of the upgrade - well, sort of
I did manage to convert all of my 2016 installs to flat file for the
mailboxes, still using 2016, which should help my situation
Apparently, the -C alt config option is somehow broken in
cyrus-2-1-sasl-v1-tail Everything installed fine, but when
