Andy Helten wrote: > Unruh wrote: >> uh, ntpdate is severely depricated, and ntpd -g is what is supposed to be >> used. If ntpd -g fails it is a bug. >> > > Then it is a bug because, as previously mentioned, no command line > argument or tinker can disable this behavior. I suppose the solution is > to skip the CLOSETIME check in clocktime() when '-g' is specified.
Andy, I agree totally: With no remote reference clocks, only local hardware, said hardware has to skip the sanity checks during that initial -g adjustment. Andy, you should go on the ntp.org site and register this as a bug! Terje -- - <[email protected]> "almost all programming can be viewed as an exercise in caching" _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
