From owner-freebsd-questions@FreeBSD.ORG Mon Jan 10 00:27:17 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E625816A4CE; Mon, 10 Jan 2005 00:27:17 +0000 (GMT) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 734D243D1F; Mon, 10 Jan 2005 00:27:17 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.13.0/8.13.0) with ESMTP id j0A0RANY013222; Sun, 9 Jan 2005 19:27:11 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Sun, 9 Jan 2005 19:27:10 -0500 To: Robert Watson , Mark From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) cc: freebsd-questions@freebsd.org Subject: Re: Freebsd 5.3 - long uptimes... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jan 2005 00:27:18 -0000 At 4:26 PM +0000 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, and >that was for a UPS-backed natbox in my parents' basement. [...] At >some point, the power went out for longer than the UPS could keep >it up, so the uptime went tumbling down... I think it was up for >about 540-550 days at that point. 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) * 599 days 14 hours (a UPS melt-down failure) * 497 days 18 hours (hard disk failure) The third one many really have been an OS failure, which I will not bother trying to describe in detail... One problem with long uptimes like that: If the system does finally die due to an OS error, it is hard to get motivated to track it down. After all, the OS has had two years worth of changes committed to it since the time you compiled the snapshot which *maybe* has an error! To remain safe when going for long uptimes like this, I had a second machine running the same release of FreeBSD, and I could build the latest snapshot of the OS on that. I would then then copy over the bits and pieces needed to keep the production system safe (such as new versions of sendmail or sshd). -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu