Mike Branda wrote:
>Explanation - (as I understand it anyway..)
>
>The www.ntp.org page said to use several lines of the server because of
>the fact that they are a pool, and a different server is assigned for
>each line. the local clock keeps things sync'd internally even if the
>whole pool at pool.ntp.org goes down. The broadcast was interesting due
>to the fact that it did not work until I set it to the actual server's
>IP. I saw several solutions that said 192.168.0.255 but that didn't
>work. if it's not the system's IP, it has to be a multicast address
>like 224.0.1.1 it seems.
>
Hrm. Weird. I don't follow the problems with .255 as broadcast.
Broadcasting to your own IP is a bit silly though - packets will never
leave your server.
Running multicast (224.0.1.1) is preferrable to broadcast anyway.
>and the drift file is a must. it isn't created
>by default according to the website so you have to do a touch to the
>file. I opted out of the internal peer thing due to the fact that I
>would have had to list out the 72 renderfarm boxes and they should still
>stay in sync because of the server's local fakeout. I will be adding the
>keys soon to secure it. the thing that started all of this that
>actually ended up screwing me up is that one of the farm boxes told me
>that it was tomorrow in a log. the snip about the ntp daemon dying if
>off by more than 1000 sec. was one of the big road blocks.
>
>
This is why I usually install ntpdate, and make sure its init script
runs before the ntp daemon does. When a system boots, making a major
correction makes sense. From that point on, it's wise to let the clock
drift gradually to sync.
>I apologize if this was drawn out. It just seems that when people
>figure stuff out because of the list help, sometimes I dont notice any
>RESOLVED posts of the solution. there have been several things that
>others have needed and I too shared that need, but never saw the final
>result.
>
>
By all means, please let us know! And for those of us who reply to
someone privately with a solution, consider Cc'ing the list to help
others who may have the same problem in the future.
- Ian C. Blenke <icblenke@nks.net>
Director of Service Delivery - Networked Knowledge Systems
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:09:57 EDT