Chris writes:
C> Long uptimes = unsecured+unpatched boxes.
C> Long uptimes? No thanks.
Most vulnerabilities are in daemons or other programs outside the
kernel, so one need not necessarily boot the machine to fix them.
--
Anthony
___
freebsd-questio
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
Garance A Drosihn wrote:
At 7:27 PM -0500 1/9/05, Garance A Drosihn wrote:
My main "production-system" use of FreeBSD is for a chat server,
which needs to be up all the time or everyone stops "chatting" and
starts yelling at me. The longest uptimes I've had so far are:
* 373 days 10 hours (a
At 7:27 PM -0500 1/9/05, Garance A Drosihn wrote:
My main "production-system" use of FreeBSD is for a chat server,
which needs to be up all the time or everyone stops "chatting" and
starts yelling at me. The longest uptimes I've had so far are:
* 373 days 10 hours (a 6-hour long power outage
At 4:26 PM + 1/9/05, Robert Watson wrote:
On Sun, 9 Jan 2005, Mark wrote:
> FreeBSD will run for years without a boot in many cases.
> Ah, this point fascinates me. Running for years? Do you ever
> have to recompile your kernel? :)
The longest personal uptime I've had is just under two years
