Date: Sun, 9 Jan 2005 21:54:57 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: Chris <racerx@makeworld.com> Cc: freebsd-questions@freebsd.org Subject: Re: Freebsd 5.3 - long uptimes... Message-ID: <p06200705be079d0ba52d@[128.113.24.47]> In-Reply-To: <41E1E4C0.1060503@makeworld.com> References: <Pine.NEB.3.96L.1050109162444.64144B-100000@fledge.watson.org> <p06200702be0769f3ab7c@[128.113.24.47]> <p06200704be07936f649b@[128.113.24.47]> <41E1E4C0.1060503@makeworld.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 8:13 PM -0600 1/9/05, Chris wrote: > >Long uptimes = unsecured+unpatched boxes. >Long uptimes? No thanks. If you had read my earlier message, you would see that I take steps to keep the important components patched, and thus my machine has been as secure as a freshly-built system. Long uptimes are just a nice goal that I try for, so if there was a security issue where I *had* to reboot to fix it, I certainly would do so. My strategy works for me because I have spare machines, and I am constantly paying attention to freebsd changes. The strategy will not work as well for people in different situations than mine. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06200705be079d0ba52d>