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

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Boris Goldberg
Date: Tuesday, October 23, 2007 - 10:05 am

Hello Pierre-Yves,

Tuesday, October 23, 2007, 11:39:10 AM, you wrote:


PYR> I hope nobody takes what you say seriously. Running rdate instead of
PYR> ntpd like you describe is wrong for many reasons which have been stated
PYR> over and over in the last few years. Please do not spread wrong
PYR> information around, and do your homework before giving others advice
PYR> on what you think is good sysadmin practice.

  The  ntpd  from  OBSD  is  raw  and lame yet. It takes days (!) to really
synchronize, adjusting time and clock frequency back and forth (even if you
start  with  -s) so it's too early to say that using it is "right". It will
be "right" after it matures, gets more useful synchronization algorithm and
it's own ntpdate (or a parameter to synchronize and exit).

-- 
Best regards,
 Boris                            mailto:boris@twopoint.com
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: Network Time Synchronization using timed or ntpd or a ..., Pierre-Yves Ritschard, (Tue Oct 23, 9:39 am)
Re: Network Time Synchronization using timed or ntpd or a ..., Boris Goldberg, (Tue Oct 23, 10:05 am)
Re: Network Time Synchronization using timed or ntpd or a ..., Darrin Chandler, (Tue Oct 23, 11:59 am)
Re: Network Time Synchronization using timed or ntpd or a ..., Martin Schröder, (Tue Oct 23, 3:44 pm)