From owner-freebsd-questions@FreeBSD.ORG Thu Oct 9 14:34:44 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 34ADE1065689 for ; Thu, 9 Oct 2008 14:34:44 +0000 (UTC) (envelope-from rvm@CBORD.com) Received: from smssmtp.cbord.com (mx1.cbord.com [24.39.174.11]) by mx1.freebsd.org (Postfix) with ESMTP id E90948FC17 for ; Thu, 9 Oct 2008 14:34:43 +0000 (UTC) (envelope-from rvm@CBORD.com) X-AuditID: ac1f0165-00000edc00000410-77-48ee1647377c Received: from Email.cbord.com ([10.1.1.100]) by smssmtp.cbord.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 9 Oct 2008 10:33:43 -0400 X-MIMEOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 9 Oct 2008 10:33:18 -0400 Message-ID: In-Reply-To: <28283d910810081851h7ab99b5y94b68f04b2a956e7@mail.gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: uptime 2 years! Thread-Index: AckpsYvSA52jzxAlQB2+2DziI4ntXwAZ+kEg References: <20081008223925.GB97321@melon.esperance-linux.co.uk><2F5A85A9-3C1C-4328-9D4C-8722B3FDB2A1@ahm-inc.com> <28283d910810081851h7ab99b5y94b68f04b2a956e7@mail.gmail.com> From: "Bob McConnell" To: "matt donovan" X-Brightmail-Tracker: AAAAAA== Cc: freebsd-questions@freebsd.org Subject: RE: uptime 2 years! X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Oct 2008 14:34:44 -0000 On Behalf Of matt donovan > why is this news or even important? heck most servers > are up longer then this. It's neither. But the discussion proved useful as it served to remind me that there are security updates that need to be reviewed periodically, even for machines that are not directly connected to the outside world. I also recorded a couple of URLs that I should review, and caught the reminder that 2038 is coming quicker than I had hoped. That was very timely, by the way. Later that same day it helped debug a problem. Yeah, we already have one web developer that has run up against that limit. He decided that forever is 30 years and wondered why QA got an error when they tried to set a schedule end date with it. No, we don't use any 64 bit OS, yet. Bob McConnell