From owner-freebsd-questions@FreeBSD.ORG Sat Feb 7 07:30:37 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16B9B16A4CE for ; Sat, 7 Feb 2004 07:30:37 -0800 (PST) Received: from mta13.adelphia.net (mta13.mail.adelphia.net [68.168.78.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id B621943D1D for ; Sat, 7 Feb 2004 07:30:36 -0800 (PST) (envelope-from Barbish3@adelphia.net) Received: from barbish ([67.20.101.119]) by mta13.adelphia.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with SMTP id <20040207153036.KBMY11569.mta13.adelphia.net@barbish>; Sat, 7 Feb 2004 10:30:36 -0500 From: "JJB" To: "Matthew Seaman" , "Earl" Date: Sat, 7 Feb 2004 10:30:35 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-reply-to: <20040207091235.GA7043@happy-idiot-talk.infracaninophile.co.uk> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: freebsd-questions@freebsd.org Subject: RE: clock not keeping time X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Barbish3@adelphia.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Feb 2004 15:30:37 -0000 I have found that when the pc fails to keep correct internal time, this is an symptom of the motherboard battery going bad. Power off PC, open case, find, and replace battery. It's looks like an thick dime. After replacing, set time manually with date command and it should be fine. -----Original Message----- From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Matthew Seaman Sent: Saturday, February 07, 2004 4:13 AM To: Earl Cc: freebsd-questions@freebsd.org Subject: Re: clock not keeping time On Fri, Feb 06, 2004 at 10:26:51PM -0600, Earl wrote: > I change the clock to the correct time. And the next day when I log in > the time is worng. How can I fix this. So that it will keep the correct > time. In general, use ntpd(8) to synch your sytem clock to various time servers on the net. This works well on a broadband or always-on connection, but be warned that it will bring up a dial-up line about every twenty minutes, so it's probably not what you want in that situation -- an alternative in that case is to use ntpdate(8) out of your /etc/ppp/ppp.linkup script. Here's a sample /etc/ntp.conf that you can probably just drop into your system. See http://fortytwo.ch/time/ for details of the 'pool.ntp.org' system. Replace the nework number and netmask in the 3rd line with the ones appropriate to your site: restrict default nomodify nopeer # Restrict access ... restrict 127.0.0.1 # ... except for me ... restrict 192.168.0.0 mask 255.255.255.0 # ... an the local net server pool.ntp.org server pool.ntp.org server pool.ntp.org pidfile /var/run/ntpd.pid driftfile /var/ntp/ntp.drift See also the lists of public stratum 2 servers at http://www.eecis.udel.edu/~mills/ntp/clock2a.html for some more servers if you need them. Plus consult your ISP -- most will make NTP servers available for their customers. To turn on NTP using the ntp.conf above in your system add: ntpdate_enable="YES" ntpdate_flags="-b -s pool.ntp.org" xntpd_enable="YES" xntpd_flags="" to your /etc/rc.conf (The 'xntpd' bit is historic -- ntpd(8) was called xntpd(8) for some time). Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK