clock too slow - big time offset with ntpdate
martin.dieringer at gmx.de
Thu May 3 00:35:47 UTC 2007
On Wed, 2 May 2007, Doug Barton wrote:
> Martin Dieringer wrote:
>> On Wed, 2 May 2007, John Walthall wrote:
>>> On Tue, May 01, 2007 at 08:50:10PM +0200, Martin Dieringer wrote:
>>>> I think it has to do with powerd, if I kill that, the time stays correct.
>>> With powerd enabled, are you able to maintain a "reasonably"
>>> correct time with frequent NTP syncronizations? Sorry if it's just
>>> me, but I am not quite clear about that, from what has been written
>> I would have to update every minute at least and would still be more
>> than 5 seconds off.
> I think you misunderstand how ntpd works vs. how ntpdate works.
> ntpd is a daemon, so you don't run it every minute, it runs in the
> background and keeps the clock up to date.
> Turn off all of the power management, and any other service that
> might be affecting the clock, and then reboot. If your system is
> able to maintain correct time under these circumstances, start
> adding things in until you find the culprit and let us know.
both laptops can keep the time without powerd. apm is enabled, but not
acpi. as soon as I start powerd or change cpu speed, time gets a few
It doesn't matter whether I use ntpd or ntpdate.
(ntpdate at system startup makes no sense as I have to dialup first).
More information about the freebsd-stable