valizade...@gmail.com wrote:
> i have a ntp server based on Raspberry Pi3 with PPS (from u-blox6 ). i have
> also added a hardware clock to this system.
>
>
> SOME times there is a large offset(3-18 sec) on the SHM (ntp driver 28).
> i did some experiments and figured out it is related to "leap
Jakob Bohmwrote:
> Posting to comp.protocols.time.ntp is automatically gatewayed (two-way)
> to questions@lists.ntp.org or questi...@ntp.org [good].
>
> questions-ow...@lists.ntp.org sends out a moderation warning e-mail when
> this happens [bad].
>
> Not sure where to report this, as it is
On 31/10/2017 18:17, William Unruh wrote:
On 2017-10-31, valizade...@gmail.com wrote:
i have a ntp server based on Raspberry Pi3 with PPS (from u-blox6 ). i have
also added a hardware clock to this system.
SOME times there is a large offset(3-18 sec) on the SHM (ntp
On 01/11/17 11:46, valizadeh...@gmail.com wrote:
local lcok is there because my system is not connected to internet and i need
to have the hwclock to keep the time during power-offs,i have disabled the pre
installed fakeclock and used an I2c connected battery backed up RTC chip.
Local clock
On 01/11/2017 11:46, valizadeh...@gmail.com wrote:
[]> local lcok is there because my system is not connected to internet
and i need to have the hwclock to keep the time during power-offs,i have
disabled the pre installed fakeclock and used an I2c connected battery
backed up RTC chip.
the
On 31/10/2017 08:50, valizade...@gmail.com wrote:
server 127.127.1.1 minpoll 3 maxpoll 4 #hwcloak
fudge 127.127.1.1 stratum 3
As Bill says, get rid of the local clock, and add some Internet sources.
That way you can check whether your GPS is grossly wrong. The reach
value seem wrong as
On 2017-10-31, valizade...@gmail.com wrote:
> i have a ntp server based on Raspberry Pi3 with PPS (from u-blox6 ). i have
> also added a hardware clock to this system.
>
>
> SOME times there is a large offset(3-18 sec) on the SHM (ntp driver 28).
What program is