the_ntp_functions
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
the_ntp_functions [2017/03/18 11:38] – [Synchronising Clients] walkeradmin | the_ntp_functions [2017/03/18 13:18] – [to do] walkeradmin | ||
---|---|---|---|
Line 190: | Line 190: | ||
\\ | \\ | ||
{{: | {{: | ||
+ | \\ | ||
\\ | \\ | ||
Select ' | Select ' | ||
Line 263: | Line 264: | ||
---- | ---- | ||
+ | \\ | ||
+ | \\ | ||
+ | |||
+ | ---- | ||
+ | ==== Clients over 1000 Seconds out of time ==== | ||
+ | \\ | ||
+ | “NTP won’t normally reset the clock if it’s off by more than 1000s. If you run: | ||
+ | < | ||
+ | ntpd -gq’ | ||
+ | </ | ||
+ | It ignores the clock being way adrift from ntp time and will force it to be correct then close. The old ntpdate program does the same thing.” | ||
+ | \\ | ||
+ | \\ | ||
+ | Credit: [[http:// | ||
+ | \\ | ||
+ | \\ | ||
+ | |||
+ | ---- | ||
==== to do ==== | ==== to do ==== | ||
Line 268: | Line 287: | ||
- | clients over 1000seconds out | ||
- | “NTP won’t normally reset the clock if it’s off by more than 1000s. | + | |
- | If you run ‘ntpd -gq’ it ignores the clock being way adrift from ntp time and will force it to be correct then close. The old ntpdate program does the same thing.” | + | |
- | credit: I found it here earlier today when I was searching on some raspi NTP issues | + | |
- | http:// | + | |
- | Reply | + |
the_ntp_functions.txt · Last modified: 2023/03/09 22:35 by 127.0.0.1