[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
OpenNTPProject.org
- Subject: OpenNTPProject.org
- From: alby.williams at verizon.com (Anthony Williams)
- Date: Mon, 17 Feb 2014 10:38:30 -0500
- In-reply-to: <CAJvB4tmxFyTLN-epeMF1CAEu_V7fHbupO=Y7GJNacKcPurZ4pw@mail.gmail.com>
- References: <[email protected]> <CAAf7UomfGfm99w1hav67dPcaYp8Ote4ex-ncdbHKTb__yO6FPQ@mail.gmail.com> <[email protected]> <[email protected]> <4B4120B1642DCF48ACA84E4F82C8E1F60103B7A00FC7@EXCH> <CF2778F9.10ABF%[email protected]> <[email protected]> <CAJvB4tmxFyTLN-epeMF1CAEu_V7fHbupO=Y7GJNacKcPurZ4pw@mail.gmail.com>
Blake:
Just to make sure I've got this down, listing a device as a "peer" in
the ntp.conf file will create a situation where both devices are saying,
"I know what time it is" and splitting the difference? Whereas when you
list a device as a "server", it's using that as the authority on the
correct time?
Example:
--
#
peer 192.168.1.1 iburst
peer 192.168.1.2 iburst
#
server ntp.colby.edu minpoll 6 maxpoll 10 iburst
server bonehed.lcs.mit.edu minpoll 6 maxpoll 10 iburst
On 2/17/2014 10:28 AM, Blake Dunlap wrote:
> Peer means it considers the other side an equal and they will mutually skew
> time together. If you have peer on for devices you don't consider your time
> servers, you're opening yourself up to problems.
>
> -Blake