Date: Tue, 22 May 2007 12:30:41 -0700 From: Chuck Swiger <cswiger@mac.com> To: Olivier Mueller <om-lists-bsd@omx.ch> Cc: freebsd-stable@freebsd.org Subject: Re: minimizing downtime on upgrades? (for example: mysql 4.1 -> 5.0 or php) Message-ID: <96A27673-F4AC-4A39-91EC-C3242F2E76A7@mac.com> In-Reply-To: <1179860619.14799.37.camel@bigapple.omnis.ch> References: <1179860619.14799.37.camel@bigapple.omnis.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 22, 2007, at 12:03 PM, Olivier Mueller wrote: > So I can only do that after the installation of mysql50-client, which > means all the services will have to be stopped during the > compilation of > mysql50-server, which usually takes some time. > > Isn't there a better way? How do you handle such cases? Pretty much as you suggest below: > Same questions for php upgrades: on php5 upgrade, all the other php5-* > packages have to be compiled too, and keeping the webserver running > during this time is probably not the best idea. > > What I'm going to try is to prepare packages of the ports I have to > upgrade on a dev/test server, and then install them with pkg_add: is > that the "right way" ? You have a build box that you generate new tarballs of the packages you want to update (via "make package", "make package-recursive", "portupgrade -p", etc), which you can then test and make sure they behave sensibly, and then use these to rapidly update your production machines with minimal downtime. -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?96A27673-F4AC-4A39-91EC-C3242F2E76A7>