From owner-freebsd-stable@FreeBSD.ORG Tue May 8 15:12:59 2007 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 668F116A403 for ; Tue, 8 May 2007 15:12:59 +0000 (UTC) (envelope-from martin.dieringer@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id A61B613C447 for ; Tue, 8 May 2007 15:12:58 +0000 (UTC) (envelope-from martin.dieringer@gmx.de) Received: (qmail invoked by alias); 08 May 2007 15:12:57 -0000 Received: from c-134-228-89.d.dsl.de.ignite.net (EHLO dieringer.dyndns.org) [62.134.228.89] by mail.gmx.net (mp028) with SMTP; 08 May 2007 17:12:57 +0200 X-Authenticated: #21464393 X-Provags-ID: V01U2FsdGVkX18OhTZwbEgOQaUzTOoz13fPVh0ljoc2uL1Xdp/uzl 1j94ixvIqKSTmu Received: (qmail 24155 invoked by uid 1001); 8 May 2007 15:12:48 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 8 May 2007 15:12:48 -0000 Date: Tue, 8 May 2007 17:12:48 +0200 (CEST) From: Martin Dieringer To: freebsd-stable@FreeBSD.ORG In-Reply-To: <711B5A41-C890-4620-9D43-25C4BD5B35F1@goldmark.org> Message-ID: <20070508170957.X839@thinkpad.dieringer.dyndns.org> References: <200705081248.l48CmvBO083216@lurza.secnetix.de> <20070508151525.Y839@thinkpad.dieringer.dyndns.org> <711B5A41-C890-4620-9D43-25C4BD5B35F1@goldmark.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Y-GMX-Trusted: 0 Cc: Subject: Re: clock problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Martin Dieringer List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2007 15:12:59 -0000 On Tue, 8 May 2007, Jeffrey Goldberg wrote: > On May 8, 2007, at 8:33 AM, Martin Dieringer wrote: > >> On Tue, 8 May 2007, Oliver Fromme wrote: >> >>> Martin Dieringer wrote: >>>> My clock is now _15 minutes_ late, after about 1 day with powerd >>>> running. >>>> ntpd is running also. >>>> Can nobody tell where the problem is here? > Also if you have other machines on your local network, you can use > them to peer with the one with the bad clock. both machines have bad clocks! > I recall some discussion earlier on this list (I think) about these > problems with powerd and clocks. The solution involved some tuning > with sysctl or something similar. I'm sorry I can't be more > specific. that was for freebsd 4 > You may also try to set things to restart ntpd on dial-up. it does not help m.