From owner-freebsd-hackers Fri Feb 28 09:13:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA06174 for hackers-outgoing; Fri, 28 Feb 1997 09:13:17 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA06169 for ; Fri, 28 Feb 1997 09:13:14 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA15049; Fri, 28 Feb 1997 10:12:37 -0700 (MST) Date: Fri, 28 Feb 1997 10:12:37 -0700 (MST) Message-Id: <199702281712.KAA15049@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Adrian Chadd Cc: freebsd-hackers@freebsd.org Subject: Re: uptime In-Reply-To: References: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I seem to remember a bug (feature? :) in Linux systems that took them down > at (around) a certain uptime *grin* Anyone confirm / deny this? Yep, but it was with older kernels. The jiffies valued overflowe after a year or so, and required you to reboot the machine. In reality, I doubt anyone ever reached the goal. Nate