OpenNTP features

2016-03-19 Thread Gabor Juhasz
Hi All, In our IoT project we have to select an NTPd for our embedded device in order it can have accurate time. It uses 3G/4G mobile net. Of course the net is expensive so we have to reduce the network usage. Currently we have 2 candidates : OpenNTPd and Chrony. In OpenNTP (5.7p4) we are missin

Re: OpenNTP features

2016-03-19 Thread lists
Wed, 16 Mar 2016 13:23:08 +0200 Gabor Juhasz > In our IoT project we have to select an NTPd for our embedded device > in order it can have accurate time. Relatively correct time within specified tolerance, not accurate. > It uses 3G/4G mobile net. Of course the net is expensive so we have to > r

Re: OpenNTP features

2016-03-18 Thread Brent Cook
> On Mar 16, 2016, at 6:23 AM, Gabor Juhasz wrote: > > Hi All, > > In our IoT project we have to select an NTPd for our embedded device > in order it can have accurate time. > It uses 3G/4G mobile net. Of course the net is expensive so we have to > reduce the > network usage. Currently we have 2 c

Re: OpenNTP features

2016-03-18 Thread Theo de Raadt
> * Maxchange > Maximum allowed offset corrected on a clock update. If the delta is > bigger ntpd exists. I don't see the purpose of that. > * Polltime > maxpoll /minpoll : setting the minimum/maximum polling interval Have you measured the actual $ cost for what it does now, and determined that