Date: Tue, 8 May 2007 17:12:48 +0200 (CEST) From: Martin Dieringer <martin.dieringer@gmx.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: clock problem Message-ID: <20070508170957.X839@thinkpad.dieringer.dyndns.org> In-Reply-To: <711B5A41-C890-4620-9D43-25C4BD5B35F1@goldmark.org> References: <200705081248.l48CmvBO083216@lurza.secnetix.de> <20070508151525.Y839@thinkpad.dieringer.dyndns.org> <711B5A41-C890-4620-9D43-25C4BD5B35F1@goldmark.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070508170957.X839>