Date: Tue, 11 Oct 2011 09:52:44 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Mike Brown <mike@skew.org> Cc: freebsd-security@freebsd.org Subject: Re: Reasonable expectations of sysadmins Message-ID: <86d3e4j777.fsf@ds4.des.no> In-Reply-To: <201110020411.p924BPqn037383@chilled.skew.org> (Mike Brown's message of "Sat, 1 Oct 2011 22:11:25 -0600 (MDT)") References: <201110020411.p924BPqn037383@chilled.skew.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Brown <mike@skew.org> writes: > Also, sometimes things go haywire after a reboot, especially after extend= ed=20 > uptime and updates to the kernel or core libraries, so I'm in the habit o= f=20 > only shutting down when necessary. So if I don't see "and then reboot" in= an=20 > update procedure - and most of the time, security updates don't require i= t -=20 > then I don't do it. Actually, this is an argument in favor of rebooting regularly, or at least after every major change, so you know the server will boot unassisted if something happens (power outage, cleaning staff tripped over the mains cable, etc.) I once spent an entire evening coaxing a mission-critical database server back up after a simple disk replacement because a predecessor had performed an in-place system upgrade without verifying that the new configuration would boot cleanly. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86d3e4j777.fsf>