Date: Sun, 23 Mar 2003 10:56:40 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: hm@kts.org (Hellmuth Michaelis) Cc: ulf@Alameda.net, lists@visionsix.com, freebsd-isp@FreeBSD.ORG Subject: Re: Production Machine, Custom Kernel, Updating to P9 Message-ID: <20030323105640.41aba4df.Alexander@Leidinger.net> In-Reply-To: <20030323080106.3D7195499@bert.int.kts.org> References: <20030322125653.V11496@seven.alameda.net> <20030323080106.3D7195499@bert.int.kts.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 23 Mar 2003 09:01:06 +0100 (CET)
hm@kts.org (Hellmuth Michaelis) wrote:
> Do you bring down the machine to single user mode for "make installworld" ?
>
> If not, what is your experience with doing a "make installworld" on a
> running system ?
I did a lot of updates without ever being in SU mode. A lot of
production class systems (the minority of them had a backup system for
failover). So far I had only 1 case (as far as I can remember), where
the update caused an interrupt of the services running on the system
(not counting the necessary reboot after the update). This case was
either the update from 3-stable to 4.1.1 or the update from 4.1.1 to 4.2
(or something like this). The cause was an incompatible change in
OpenSSL without a library version bump (which wasn't a problem because
of the installworld in MU mode). Even if this particular problem wasn't
known in advance to me, I expected to have a 'problem' with this
particular update, so the update was done at a time where a 'hickup'
wouldn't have a huge impact.
If you want to go the safe route, you maybe want to redefine INSTALL to
"install -S" in make.conf (I did every update without redefining it so
far, but maybe this will change... just to be on the safe side).
And for the general audience:
You should have enough free space on the disk(s) off course (specially
on a softupdates enabled slice), else the installworld may fail, but
this is a general problem again and not particular to a installworld in
MU mode.
BTW.: Everyone who updates from 4.6: watch out for old MySQL start
scripts (the contain the sequence "& &&" in one line, workaround: split
the line after the first '&' and remove "&&"), they will fail to start
MySQL after the update to 4.7.
Bye,
Alexander.
--
Reboot America.
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030323105640.41aba4df.Alexander>