[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: System clock



my 2c

The previously mentioned OSX time setting feature has caused me some
grief with ntpd. ntpdate did not seem to be better behaved either.
However, the whole thing goes bezerk when you let your powerbook die
with an exhausted battery.

ntpd works for me, OSX does also have a time server setting and with
luck if you use the same one they seem to track (from my experience).
ntpd will die if the offset exceeds some limit (maybe 1hr??). you can
track ntpd with ntpq or ntpdc

apt-get ntp-simple 

david

On Tue, 2004-07-20 at 21:36, Geert Uytterhoeven wrote:
> On Tue, 20 Jul 2004, Paul van Tilburg wrote:
> > On Tue, Jul 20, 2004 at 11:46:07AM +0100, Sebastian Tennant wrote:
> > > 	My system clock is losing about 15 minutes a week.  Any ideas why this
> > > might be?  A battery perhaps?  Or is it normal?  If I remember rightly OSX
> > > uses some sort of network time server to set the system clock.  Is there an
> > > equivalent GNU/Linux compatible service out there?
> >
> > I'm experiencing the same problem, not only when coming back from
> > suspend. ntp-server is doing all kinds of stuff, but seems to refuse to
> > do anything with my clock, running ntpdate works. This problem was
> > introduced since 2.6 for me.
> 
> Plain ntp refuses to change the system clock if it's too far off. Ntpdate
> always updates the clock to the correct time.
> 
> Gr{oetje,eeting}s,
> 
> 						Geert
> 
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
> 
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> 							    -- Linus Torvalds
-- 
-------------------------------------------------------
David Howe
www.qednet.biz
davidATqednet.biz
-------------------------------------------------------





Reply to: