Re: Network Time Synchronization using timed or ntpd or a Combination?

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Boris Goldberg <boris@...>
Cc: <misc@...>
Date: Thursday, October 25, 2007 - 1:10 pm

On 10/25/07, Boris Goldberg wrote:

no, it's not making an argument for a one-shot sync attempt in ntpd.
that's what "rdate -na" is for. ntpd is for those who care that their
clock remains close to an authoritative source of time.

synchronization isn't a one-time thing. it's an ongoing process. a
peecee isn't a terribly controlled environment - you have electrical
noise, temperature changes, processor loads, interrupts ... all of
which make it very difficult to keep time on a free-running clock.

CK

--
GDB has a 'break' feature; why doesn't it have 'fix' too?

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: Network Time Synchronization using timed or ntpd or a Co..., Chris Kuethe, (Thu Oct 25, 1:10 pm)
Re: Network Time Synchronization using timed or ntpd or a Co..., Pierre-Yves Ritschard, (Tue Oct 23, 12:39 pm)