> On May 12, 2006, at 7:41 AM, Simon Matter wrote: > >>> The other thing that you might want to be aware of is the BDB >>> versions >>> on both RH boxes. In the past, after an rsync, I've had to fiddle >>> with >>> the berkeley dbs for deliver.db and a few others I don't recall at >>> the >>> moment... >>> >>> I usually do a test run, rsync everything and connect to the new box, >>> then have a script handy that shuts down both servers, rsyncs, >>> then does >>> any db_recover/upgrade, etc. then brings up the new server...this way >>> you can minimize down time. >> >> That's exactly what my rpms handle but those shipped with RHEL >> don't :) > > I'm glad I asked. I'll work on the upgrade. > > Now for a related question: > > If I update the RHEL3 machine's 2.2.8 to 2.2.12 from the src.rpm, are > there any gotchas there? I never had any problems. However, as I said, if you want to use my rpms I strongly suggest to take the current 2.3.3 package. If you don't use the RHEL4 package anyway, there's no reason to stay with 2.2. Simon ---- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
