Date: Wed, 20 Apr 2005 22:04:11 +0200 From: Matthias Buelow <mkb@incubus.de> To: Bill Moran <wmoran@potentialtech.com> Cc: jim-c@charter.net Subject: Re: Newbie Question About System Update Message-ID: <200504202004.j3KK4BdA003074@drjekyll.mkbuelow.net> In-Reply-To: Message from Bill Moran <wmoran@potentialtech.com> <20050419120053.6ad17df1.wmoran@potentialtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Bill Moran <wmoran@potentialtech.com> 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. >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. mkb.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200504202004.j3KK4BdA003074>