From owner-freebsd-questions@FreeBSD.ORG Mon Apr 20 23:38:32 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 95D96106564A for ; Mon, 20 Apr 2009 23:38:32 +0000 (UTC) (envelope-from fsb@thefsb.org) Received: from smtp194.iad.emailsrvr.com (smtp194.iad.emailsrvr.com [207.97.245.194]) by mx1.freebsd.org (Postfix) with ESMTP id 6D24C8FC21 for ; Mon, 20 Apr 2009 23:38:32 +0000 (UTC) (envelope-from fsb@thefsb.org) Received: from relay19.relay.iad.mlsrvr.com (localhost [127.0.0.1]) by relay19.relay.iad.mlsrvr.com (SMTP Server) with ESMTP id D9F341B4055; Mon, 20 Apr 2009 19:38:31 -0400 (EDT) Received: by relay19.relay.iad.mlsrvr.com (Authenticated sender: fsb-AT-thefsb.org) with ESMTPSA id BC26D1B4027; Mon, 20 Apr 2009 19:38:31 -0400 (EDT) User-Agent: Microsoft-Entourage/12.10.0.080409 Date: Mon, 20 Apr 2009 19:38:26 -0400 From: Tom Worster To: Matthew Seaman Message-ID: Thread-Topic: portmaster -a on a live server Thread-Index: AcnCERnPJ3ouqxnRNUe1fwV4SWGcAw== In-Reply-To: <49ECC7A5.8020002@infracaninophile.co.uk> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: portmaster -a on a live server X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Apr 2009 23:38:32 -0000 On 4/20/09 3:06 PM, "Matthew Seaman" 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.