On Tue, Sep 9, 2008 at 2:52 PM, Richard B. Gilbert
[EMAIL PROTECTED] wrote:
FWIW, a system that has been
synchronized by NTP will tend to stay close to the correct time for a
reasonable period of time as long as the environment does not change
significantly. If the network fails AND the air
Danny Mayer wrote:
Kay Hayen wrote:
And iburst and minpoll=maxpoll=5 to improve the results.
This indicates that you don't understand NTP. You should never ever
change the minpoll and maxpoll values unless you understand the NTP
algorithms in detail and understand the consequences of
Danny Mayer [EMAIL PROTECTED] wrote:
Rick Jones wrote:
If it simply sends via the socket on which the query was recieved,
having bound that socket to a given IP should result in that IP being
used as the source IP of the response.
Perhaps there is a reason to send via another socket,
[EMAIL PROTECTED] (Danny Mayer) writes:
...
Briefly, you use the defaults for MINPOLL and MAXPOLL. You may use the
iburst keyword in a server statement for fast startup. You may use
the burst keyword ONLY with the permission of the the server's owner.
99.99% of NTP installations will work
On Mon, 6 Oct 2008 14:29:41 GMT in comp.protocols.time.ntp,
[EMAIL PROTECTED] (Gretchen Baxter) wrote:
I am doing research for my employer around time synchronization.
I have found a lot of good information at http://www.usno.navy.mil
But does the EU or other European countries have a similar
David,
You have a very good point. Orphan mode has been around for more than a
year and has been carefully described in the online documentation and
snapshots. Users of the release version, which is a cherrypicked but
incomplete extract of various fixes and improvements over the year, may
