This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links
SNTP
SNTP

Version management

Difference between version and

At line 1 added 20 lines
!!! Overview
[{$pagename}] is an [Abbreviation] for [Simple Network Time Protocol][{$pagename}] is a subset of [Network Time Protocol] ([NTP]) and is intended for primary servers equipped with a single reference clock, as well as for [clients] with a single upstream [server] and no dependent [clients].As a result of many issues with keeping [Why is Time Important] using [NTP] and the added requirements, we have almost given up on ntp usage.
We have had much better success using sntp.
We have determined that we have better time control if we use one server to use ntp to contact a ntp server and all other network machines use sntp and cron to update their local clock. We do this by adding a cron command similar to:
{{{
*/5 * * * * root /usr/sbin/sntp -P no -r 192.168.1.1 >/dev/null 2>&1
}}}
for all the other servers not running ntp.
The "-P no" prevents prompting if the user for time changes outside of the maximum value (default 30 seconds.)
This solution sets the local clock on the machine to the correct time from the locally available ntp server which typically gets its time from a known, low stratum ntp server. We also often stop and disable the ntp damon on the server.
Let us know what you have done or run into with ntp.
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthorTop