Исходное сообщение
"Ntp. Как переживает клиент, если эталонные часы скакнули?" Отправлено stereoPANDA, 01-Авг-13 15:53
На ntp.org пишут, что : What happens if the Reference Time changes? Ideally the reference time is the same everywhere in the world. Once synchronized, there should not be any unexpected changes between the clock of the operating system and the reference clock. Therefore, NTP has no special methods to handle the situation. Instead, ntpd's reaction will depend on the offset between the local clock and the reference time. For a tiny offset ntpd will adjust the local clock as usual; for small and larger offsets, ntpd will reject the reference time for a while. In the latter case the operation system's clock will continue with the last corrections effective while the new reference time is being rejected. After some time, small offsets (significantly less than a second) will be slewed (adjusted slowly), while larger offsets will cause the clock to be stepped (set anew). Huge offsets are rejected, and ntpd will terminate itself, believing something very strange must have happened. Naturally, the algorithm is also applied when ntpd is started for the first time or after reboot. Вопросы следующие: tiny offset = конкретно сколько? small offset = конкретно сколько? huge offset = конкретно сколько? Как эти параметры можно задать? Спасибо.

Ваше сообщение
Имя*:
EMail:	Для отправки новых сообщений в текущей нити на email укажите знак ! перед адресом, например, !user@host.ru (!! - не показывать email). Более тонкая настройка отправки ответов производится в профиле зарегистрированного участника форума.
Заголовок*:
Сообщение*:	> На ntp.org пишут, что : > What happens if the Reference Time changes? > Ideally the reference time is the same everywhere in the world. Once > synchronized, there should not be any unexpected changes between the clock > of the operating system and the reference clock. Therefore, NTP has > no special methods to handle the situation. > Instead, ntpd's reaction will depend on the offset between the local clock > and the reference time. For a tiny offset ntpd will adjust > the local clock as usual; for small and larger offsets, ntpd > will reject the reference time for a while. In the latter > case the operation system's clock will continue with the last corrections > effective while the new reference time is being rejected. After some > time, small offsets (significantly less than a second) will be slewed > (adjusted slowly), while larger offsets will cause the clock to be > stepped (set anew). Huge offsets are rejected, and ntpd will terminate > itself, believing something very strange must have happened. > Naturally, the algorithm is also applied when ntpd is started for the > first time or after reboot. > Вопросы следующие: > tiny offset = конкретно сколько? > small offset = конкретно сколько? > huge offset = конкретно сколько? > Как эти параметры можно задать? > Спасибо.
	Введите код, изображенный на картинке: