On Sun, 2007-03-25 at 14:26 -0700, Darrin Chandler wrote: > Have you measured the time from ntpd startup until it logs `clock is now > synced' in the log? On the same machine, I see anywhere from 10 minutes > to about 1 hour. In normal cases, machines acting as time servers are > always on. If it takes less than an hour for ntpd to sync, and then it's > up for months at a time then there's little problem.
I left OpenNTPd running over the weekend and it wasn't synced this morning. Today I've manually changed time 30 minutes in the past and then run ntpd -s. Now It seems to report it is synced to the clients. > If you want to turn on a computer and have it fetch some times from the > network and report that it's synced... well, that's not accurate. A big, > full-blown, complex thing like xntpd won't do it, either. > If you don't really care what time it is, but want all your local > computers to have the same time (or very, very close) there are other > ways such as timed(8). Then you can have a computer using ntpd, and > synced or not it can be a timed master for your network. No, I'd like the clock to be synced and as accurate as possible. But not being able to sync at all is quite bad.
