From owner-freebsd-questions Mon Dec 22 16:56:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA15695 for questions-outgoing; Mon, 22 Dec 1997 16:56:17 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from dancinman.com (dancinman.com [204.91.116.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA15687 for ; Mon, 22 Dec 1997 16:56:06 -0800 (PST) (envelope-from sal@dancinman.com) Received: from localhost (sal@localhost) by dancinman.com (8.8.3/8.8.3) with SMTP id TAA23354; Mon, 22 Dec 1997 19:56:45 -0500 (EST) Date: Mon, 22 Dec 1997 19:56:44 -0500 (EST) From: Sal To: Jonathan Fosburgh cc: freebsd-questions@FreeBSD.ORG Subject: Re: machine freezes up In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Dec 1997, Jonathan Fosburgh wrote: > This is a problem I had with 2.2.5R. I upgraded to the December 14 > snapshot of 2.2 and now it has been up almost 3 and a half days for the > first time in ages. If there was an inheren problem in 2.2.5, it > *appears* to be fixed. (Note, as of the December 11 snapshot, I still had > this problem) I will give this a try... hopefully it will work... > While on your network you can use ntpdate. This will check with the clock > servers you specify. A few that I use are www.freebsd.org, www.uh.edu, > and clock.psu.edu. Apparently it does not matter if they are in the same > timezone as you. Once I get the system up and running, I'll try this too... Wish me luck! -S -= -=- =- -= Sal Robertson =- -= sal@dancinman.com =- -= -=- =-