From owner-freebsd-stable@FreeBSD.ORG Fri Apr 22 14:09:12 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BF8316A4CF for ; Fri, 22 Apr 2005 14:09:12 +0000 (GMT) Received: from internet.potentialtech.com (h-66-167-251-6.phlapafg.covad.net [66.167.251.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEF3443D60 for ; Fri, 22 Apr 2005 14:09:11 +0000 (GMT) (envelope-from wmoran@potentialtech.com) Received: from localhost (pa-plum-cmts1e-68-68-113-64.pittpa.adelphia.net [68.68.113.64]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by internet.potentialtech.com (Postfix) with ESMTP id 991D869A22; Fri, 22 Apr 2005 10:09:10 -0400 (EDT) Date: Fri, 22 Apr 2005 10:09:09 -0400 From: Bill Moran To: Matthias Buelow Message-Id: <20050422100909.48e63ba8.wmoran@potentialtech.com> In-Reply-To: <200504202004.j3KK4BdA003074@drjekyll.mkbuelow.net> References: <20050419120053.6ad17df1.wmoran@potentialtech.com> <200504202004.j3KK4BdA003074@drjekyll.mkbuelow.net> Organization: Potential Technologies X-Mailer: Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org cc: mkb@incubus.de cc: jim-c@charter.net Subject: Re: Newbie Question About System Update X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 14:09:12 -0000 Matthias Buelow wrote: > Bill Moran writes: > > >Fact is, trying to update a running system could result in silent failures. > >The system can not replace programs that are in use, so there's always the > >chance that something or other won't get updated (cron would be an excellent > >example ... do you always shut cron off when you update? How about syslogd?) > > This is complete nonsense. Yes, and no. As was pointed out, the install process does not "cp", so it doesn't have to deal with this problem. I was wrong. However, it's still true that you can't copy over an executable in use, it's just easy to work around it. > >On a production system, you should have a serial terminal connected so you > >can go to single-user mode remotely to do updates. There are fairly > >inexpensive serial terminal boxes available from a number of vendors, and > >if you have a spare machine available, you can always hook it up as a > >serial terminal. > > I was talking about a colocation situation, where you most likely will > never see the machine. Networked console boards are usually available > but may not always be cost effective. I would agree that such a board > may be a necessity in a high profile production server but if you are a > small company, or use a machine privately, the extra cost often > outweighs the gain. And a good colo hoster usually also has qualified > staff. Who are you using for colo? I'd like to contact them. Unless your server is utterly unimportant, the last thing you want to have happen is an upgrade where the kernel doesn't boot and you have a dead system until someone can hook a console to it. Most colos I've seen charge you a premium to have someone hook a console up for you. I asked one how much it would cost to hook up a serial console and give it an IP for one month, and their response was "we don't do that, you have to pay our tech $160/hour to sit on the phone with you and enter what you want." While this seems to be a worst case scenerio, it doesn't seem to be an uncommon attitude. A lesson to all of you, when you choose a colo, don't just look at the cost of having your box sit there - estimate the cost of doing maintenance and handling problems, those are hidden costs where many colos will rape you. -- Bill Moran Potential Technologies http://www.potentialtech.com