Danny Mayer wrote:
On 6/16/2010 5:22 PM, Maarten Wiltink wrote:
Marcelo Pimenta marcelopiment...@gmail.com wrote in message
news:aanlktilq6m8apeoasibr-o8mhwifqkfv9xyf6mudr...@mail.gmail.com...
[...]
The NTP algorithm is much more complicated than the SNTP algorithm.
The short, short version:
On 7/8/2010 2:50 AM, David Woolley wrote:
Danny Mayer wrote:
On 6/16/2010 5:22 PM, Maarten Wiltink wrote:
Marcelo Pimenta marcelopiment...@gmail.com wrote in message
news:aanlktilq6m8apeoasibr-o8mhwifqkfv9xyf6mudr...@mail.gmail.com...
[...]
The NTP algorithm is much more complicated than
Hi,
i'm new here and have a question I couldn't answer by myself by
searching the internet and reading the documentation for hours.
I have a DCF77 Clock connected to the UART. The line in the ntp.conf
looks like this:
server 127.127.8.0 mode 5 prefer
Receiving the time works, but when I
Hi,
i'm new here and have a question I couldn't answer by myself by
searching the internet and reading the documentation for hours.
I have a DCF77 Clock connected to the UART. The line in the ntp.conf
looks like this:
server 127.127.8.0 mode 5 prefer
Receiving the time works, but when I disconnect
Danny Mayer ma...@ntp.org wrote:
There has been no attempt to redefine SNTP. RFC 2030 is 15 years old so
it's hardly recent. Tools like ntpdate are not SNTP clients by the
definitions of any RFC you care to name, it just sets the clock. SNTP is
a simplified protocol to discipline the clock and
Matuschka, Sebastian sebastian.matusc...@gcd-solutions.de wrote:
Hi,
i'm new here and have a question I couldn't answer by myself by
searching the internet and reading the documentation for hours.
I have a DCF77 Clock connected to the UART. The line in the ntp.conf
looks like this:
server
Matuschka, Sebastian wrote:
Hi,
i'm new here and have a question I couldn't answer by myself by
searching the internet and reading the documentation for hours.
I have a DCF77 Clock connected to the UART. The line in the ntp.conf
looks like this:
server 127.127.8.0 mode 5 prefer
Receiving the
David,
The basic definition of SNTP has not changed over the yeas, although
rfc5905 does clarify the intended scope and role of primary servers,
secondary servers and clients. It was the expected, but not required,
model that the Unix adjtime() system call be used if the offset was less
than
Danny Mayer wrote:
RFC 2030, which RFC5905 obsoleted, said the same thing. It doesn't
The substring disci appears nowhere in RFC 2030; together with failing
to find anything of the sort in a quick skim, and a specific skim of the
wording around the word clock!, I conclude that RFC 2030
