From owner-freebsd-questions Wed Nov 12 14:09:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA14373 for questions-outgoing; Wed, 12 Nov 1997 14:09:02 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from mybsd.mybsd.net (citytelprct80.citytel.net [204.244.99.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA14364 for ; Wed, 12 Nov 1997 14:08:58 -0800 (PST) (envelope-from kwoody@citytel.net) Received: from mybsd.net (mybsd.net [192.168.0.2]) by mybsd.mybsd.net (8.8.5/8.8.5) with SMTP id NAA05605; Wed, 12 Nov 1997 13:48:02 -0800 (PST) Date: Wed, 12 Nov 1997 13:48:02 -0800 (PST) From: Kwoody X-Sender: kwoody@mybsd.net To: Matthew Hunt cc: Greg Fraize , questions Subject: Re: setting the time on FreeBSD 2.2.5 In-Reply-To: <19971111151207.43860@rh.psu.edu> 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 > If you have a working network connection (even a modem) on the machine, > it is probably easier and more accurate to set the clock from another > machine running NTP: > > ntpdate clock.psu.edu > > ("clock.psu.edu" is a perfectly good example; your ISP, company, or > whatnot may have its own that you can use). > > Both methods must be done as root; you obviously don't want just anyone > changing the date on you. Just FYI, I did that a few days ago and my clock was out about 30 mins from the ntp server I did the update from and as I was in an xterm the screensaver kicked in after the time had been updated. Kinda freaked me out for a second until I realized what had happend. Keith