-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 13/08/2010 23:06, Jerry Franz wrote:
> On 8/12/2010 8:03 PM, Les Mikesell wrote:
>> Warren Young wrote:
>>>
>>> The strategy I recommended is based on the fact that its worst case
>>> behavior (a small negative jump every hour) is not a problem for me. If
>>> it is a problem for your application, you need a different design.
>>
>> It's a bad idea in the general case. If you have scheduled jobs, ntpdate may
>> jump the clock enough to miss the trigger or run them twice, where ntpd always
>> tries to move the clock fractional seconds at a time so as not to let that
>> happen. Plus, ntpdate does no sanity check at all - if the clock source is
>> badly off, the client will follow blindly even if it goes to the wrong century.
>>
>
> Whereas ntpd will simply quietly fail to sync at all if it is more than
> a few minutes off. ;)
I believe it will not fail if you tell it to
tinker panic 0
Regards, Markus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkxlYuAACgkQYoWFBIJE9eX6XwCdEx1nr9Q9dSnsfryAe1jHjmq/
92AAoJEF9++NS2J+i+9/6FQIpstXNhho
=5mox
-----END PGP SIGNATURE-----
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
