From owner-freebsd-questions Thu Dec 14 15:30:11 2000 From owner-freebsd-questions@FreeBSD.ORG Thu Dec 14 15:30:07 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id A301B37B402 for ; Thu, 14 Dec 2000 15:30:06 -0800 (PST) Received: (qmail 41522 invoked by uid 100); 14 Dec 2000 23:30:05 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14905.22525.863605.264973@guru.mired.org> Date: Thu, 14 Dec 2000 17:30:05 -0600 (CST) To: "James Lim" Cc: Subject: Re: Netcraft In-Reply-To: <000e01c06624$016ab4c0$2e189cca@sleipnir> References: <14905.20342.21687.243168@guru.mired.org> <000e01c06624$016ab4c0$2e189cca@sleipnir> X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG James Lim types: > If i am not wrong..as i have read somewhere before.. > that problem occurs arnd older version of Linux In that case, here's a SWAG: Netcraft's method of reading uptime from FreeBSD is the same as they use for Linux, the "configuration" change is to install linux emulation, and the bug of rolling over every 497 days is inherited from Linux. And I'll be *very* surprised if this is really the case - but someone might investigate it. James Lim > Technical Support Executive > > Pacific Internet Limited > 89 Science Park Drive > #02-05/06 The Rutherford > Singapore 118261 > > Finger evilfry@sg.freebsd.org for PGP key. > > ----- Original Message ----- > From: "Mike Meyer" > To: > Sent: Friday, December 15, 2000 6:53 AM > Subject: Re: Netcraft > > > > Vandenhouten Jeremy-JVANDEN1 > types: > > > From Netcraft: > > > > > > Operating systems we can usually work out uptimes for are: > > > > > > FreeBSD [but not the default configuration in versions 3 and later] > > > > > > Additionally, NT4 uptimes cycle back to zero after 49.7 days, and > > > give timestamps exactly as if the machine had been rebooted at this > > > precise point, while HP-UX, Linux, Solaris and recent releases of > > > FreeBSD also cycle back to zero after 497 days. > > > > > > Has anyone been looking into these issues, or know how to solve > > > the "default configuration problem?" > > > > I don't think so; but if you tell us how you get uptimes, we might be > > able to provide more information. > > > > The "497 day" cycle strikes me as odd. I'm sure I've seen people > > claiming longer uptimes than that... > > > > > -- > > Mike Meyer http://www.mired.org/home/mwm/ > > Independent WWW/Unix/FreeBSD consultant, email for more information. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > -- Mike Meyer http://www.mired.org/home/mwm/ Independent WWW/Unix/FreeBSD consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message