minimizing downtime on upgrades? (for example: mysql 4.1 - 5.0 or php)

2007-05-22 Thread Olivier Mueller
Hello, Some freebsd-beginner questions about how to maintain a production server up to date day after day, with a practical example: now I have to update a 6.1-based server from mysql 4.1 to mysql 5.0, minimizing the downtime during the upgrade. In the past under other OS'es I would have

Re: minimizing downtime on upgrades? (for example: mysql 4.1 - 5.0 or php)

2007-05-22 Thread Volker
On 05/22/07 21:03, Olivier Mueller wrote: Some freebsd-beginner questions about how to maintain a production server up to date day after day, with a practical example: now I have to update a 6.1-based server from mysql 4.1 to mysql 5.0, minimizing the downtime during the upgrade. In the

Re: minimizing downtime on upgrades? (for example: mysql 4.1 - 5.0 or php)

2007-05-22 Thread Chuck Swiger
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

Re: minimizing downtime on upgrades? (for example: mysql 4.1 - 5.0 or php)

2007-05-22 Thread Ulrich Spoerlein
Olivier Mueller wrote: Isn't there a better way? How do you handle such cases? We go to extra lengths and allow only pkg installs on servers. That way we are sure, that no random library pollution takes place. It also makes stuff better reproducable. Sadly packages are somewhat neclected and

Re: minimizing downtime on upgrades? (for example: mysql 4.1 - 5.0 or php)

2007-05-22 Thread Tom Judge
Chuck Swiger wrote: 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