[EMAIL PROTECTED] (Danny Mayer) wrote: > Additionally there is evidence that the server sometimes gives a totally > incorrect answer but it's not clear to anyone why.
It appears to be to discourage people from using ntpdate! > I'd have to check the ntpdate code but I don't think it does anything > special to verify the receive data. Yes, or you could try the documentation: http://www.eecis.udel.edu/~mills/ntp/html/ntpdate.html "ntpdate sets the local date and time by polling the Network Time Protocol (NTP) server(s) given as the server arguments to determine the correct time. It must be run as root on the local host. A number of samples are obtained from each of the servers specified and a subset of the NTP clock filter and selection algorithms are applied to select the best of these. Note that the accuracy and reliability of ntpdate depends on the number of servers, the number of polls each time it is run and the interval between runs." -- Ronan Flood <[EMAIL PROTECTED]> working for but not speaking for Network Services, University of London Computer Centre (which means: don't bother ULCC if I've said something you don't like) _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
