From owner-freebsd-advocacy Fri Apr 20 12: 0: 6 2001 Delivered-To: freebsd-advocacy@freebsd.org Received: from q.closedsrc.org (ip233.gte15.rb1.bel.nwlink.com [209.20.244.233]) by hub.freebsd.org (Postfix) with ESMTP id 1D73E37B422 for ; Fri, 20 Apr 2001 12:00:03 -0700 (PDT) (envelope-from lplist@closedsrc.org) Received: by q.closedsrc.org (Postfix, from userid 1003) id 5B53055407; Fri, 20 Apr 2001 11:54:22 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by q.closedsrc.org (Postfix) with ESMTP id 4BCDA51610; Fri, 20 Apr 2001 11:54:22 -0700 (PDT) Date: Fri, 20 Apr 2001 11:54:22 -0700 (PDT) From: Linh Pham To: Cc: Subject: Re: top uptime! In-Reply-To: <3AE07CBF.13F6A56D@buckhorn.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-04-20, Bob Martin scribbled: # I don't know that I really trust these uptimes all that much, except in # a general way. Also note the disclaimer "For performance reasons, we # limit this monitoring process to the most frequently requested sites." # could have more than a little to do with which OS's makes the list. I wouldn't trust them a bit... Slashdot and several other discussion boards have had nice discussions about some of the uptimes. I think they do it on pings and if anything about the server changes for some reason. Definitely doesn't work very well (invalid uptimes like: longer uptimes, etc.) if the domain is hosted behind a load balancer, proxying firewall, et al. A better way to measure uptime is to run an script on a machine that gets the output of `uptime' and sends that with an ID of the server to a central DB. -- Linh Pham [lplist@closedsrc.org] // 404b - Brain not found To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message