From owner-freebsd-chat Fri Apr 19 10:01:02 1996 Return-Path: owner-chat Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA17579 for chat-outgoing; Fri, 19 Apr 1996 10:01:02 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA17570 for ; Fri, 19 Apr 1996 10:00:59 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id KAA20170; Fri, 19 Apr 1996 10:00:20 -0700 (PDT) To: me@tartufo.muc.ditec.de (Michael Elbel) cc: chat@freebsd.org Subject: Re: How's that look for an uptime? In-reply-to: Your message of "Fri, 19 Apr 1996 16:41:36 +0200." Date: Fri, 19 Apr 1996 10:00:20 -0700 Message-ID: <20168.829933220@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-chat@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > (601) uname -a > FreeBSD tick.muc.ditec.de 2.1-STABLE FreeBSD 2.1-STABLE #0: Mon Nov 6 15:59: 54 MET 1995 me@tick:/1/src/sys-src/sys/compile/tick i386 > (602) uptime > 4:36PM up 101 days, 2:37, 5 users, load averages: 0.02, 0.02, 0.00 > > > Basically the thing has been up since we remade the kernel in November. > Not that it's allways idling around, it is our main internal www and ftp > server as well as the general web development machine :) > > I don't think I've seen uptimes that long on many other systems I've been > on. Cool - why not post your hardware configuration since that seems to be as much a function of stability as the OS running on it? :-) Jordan