From owner-freebsd-questions@FreeBSD.ORG Sat Aug 12 12:31:38 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 EE50516A4DE for ; Sat, 12 Aug 2006 12:31:38 +0000 (UTC) (envelope-from girish1729@yahoo.com) Received: from web35615.mail.mud.yahoo.com (web35615.mail.mud.yahoo.com [66.163.179.154]) by mx1.FreeBSD.org (Postfix) with SMTP id 8366043D45 for ; Sat, 12 Aug 2006 12:31:38 +0000 (GMT) (envelope-from girish1729@yahoo.com) Received: (qmail 31185 invoked by uid 60001); 12 Aug 2006 12:31:38 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=U89GknmZJQ5KFa4cEokhMDl9WcQ0jGdwtYyNFXqP2K0YMuzsA1JoIi+02zjsmuXryipDyE3xrLrSPdH1n7Lf+auD2Nx29oapMr/5C0ukOQ9DVpQoHQ4RPe9JiCJufnmvw7KxpGErxZAL3UUZgfgANRQdU2iqh/crO5+3sDUd4Hs= ; Message-ID: <20060812123138.31183.qmail@web35615.mail.mud.yahoo.com> Received: from [59.92.97.150] by web35615.mail.mud.yahoo.com via HTTP; Sat, 12 Aug 2006 05:31:38 PDT Date: Sat, 12 Aug 2006 05:31:38 -0700 (PDT) From: Girish Venkatachalam To: "P.U.Kruppa" In-Reply-To: <20060812141802.M1240@www.pukruppa.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: "P.U.Kruppa" , freebsd-questions@freebsd.org Subject: Re: Bad system clock X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Aug 2006 12:31:39 -0000 --- "P.U.Kruppa" wrote: > On Sat, 12 Aug 2006, Girish Venkatachalam wrote: > > > Hello Girish! > > > --- "P.U.Kruppa" wrote: > > > >> Hi, > >> > >> for some time now my system clock really goes > wrong > >> (some hours > >> per day). Is there some simple way to find out if > >> this is caused > >> by a hardware or software problem? > >> By "simple" I mean without installing a different > OS > >> or buying a > >> new computer? > > My God! Buying a new computer is a simple > solution? > > :-) > > > > I think for a few Euro cents or DM you can simply > buy > > yourself a new CMOS battery and you should be set. > Wouldn't there be a complaint about low battery or > something > during boot up? Not always. > > > > > You have not given enough details about your > problem. > I can't: it's just my clock going wrong. > > > Did you try installed ntp? > Yes, it doesn't help. ntpdate will set the clock > correctly at > boot time but soon afterwards it's all bad again. > ntpdate is a one time affair. It only helps correct things when they go grievously wrong (like your case for instance). Whereas if you run ntpd then it polls a server, I use ptbtime1.ptb.de, then your clock will be corrected roughly every 17 mins(1024s) thus mitigating your problem. The real solution however lies in figuring out why your clock is getting offset by several hours. A single line in /etc/ntp.conf that says server ptbtime1.ptb.de should do the trick; after installing the ntp port or package of course. Best, Girish > Uli. > > > ********************************************* > * Peter Ulrich Kruppa - Wuppertal - Germany * > ********************************************* > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com