On 4/20/09 3:06 PM, "Matthew Seaman" <m.sea...@infracaninophile.co.uk>
wrote:
> Many ports will shut down a running instance of themselves when upgraded
> like this specifically to avoid the sort of complications that can occur
> when the running image does not match what is on disk.
>
> mysql does, apache doesn't.
>
> So upgrade mysql-server last thing before you reboot.
so i'll try
portmaster -a -x mysql-server
portmaster mysql-server
reboot
which might work ok as mysql-server is a leaf node in my config
> Although I know you're
> not using portupgrade, this snippet from pkgtools.conf has been a blessing in
> minimizing outage lengths during updates on live servers:
>
> AFTERINSTALL = {
> '*' => proc { |origin|
> cmd_start_rc(origin)
> },
> }
>
> Of couse, the best course of action is to plan sufficient downtime that you
> can do the upgrades comfortably plus recover from any number of ways things
> might go wrong, but sometimes that simply isn't possible.
it's finding the optimum between minimizing downtime and having enough that
i'm trying to think through.
thanks for your remarks.
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
