[email protected] (Hal Murray) writes:
>>Seemed I made myself not totally clear: The system has NO network connection >>to the outside world, but will be the time source of a little network. (NOT >>internet-connected, for security reasons.) NTPDATE (which is deprecated >>anyway) does not work with reference clocks, it can query servers >>only. 'ntpd -g does not work, because clocks are treated different from >>servers and the code of NTPD inhibits corrections of more than CLOSETIME >>(4h) difference. >> >>So basically it looks like we would have to bypass sanity checks when '-g' >>is given. >Or write a small program that does talk to your refclock >and sets the time. Then run it before starting ntpd. That is of course rediculous since that is what ntp -g is supposed to do. REplying to a bug report that you can write your own program is true, but not helpful. Removing the CLOSETIME check would seem the simplest thing to do. >-- >These are my opinions, not necessarily my employer's. I hate spam. _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
