[no subject]

[артур хайруллин]

Hello, Garry! Thank you for your answer

 

I have some progress in solving this issue.

 

i rebuild gpsd-3.20 twice, first time i switched off writing to SHM0 and second time to SHM1

after that I record SHM0 and SHM1 data when gpsd was running into different logs

 

> All you need is to call ntp_write(). Call it with the SHM pointer, the
> "real" time and "clock" time. Done. Converting that to python will be
> interesting.

 

Next step was to write code putting above logs to SHM0 and SHM1 respectively.

After all i stopped gpsd and launched those binaries.

 

> chronyd is better tuned to working with just one source. But no reason
> NTPsec can't be improved.

 

I use ntp daemon build from ntp 4.2.6 sources.

 

Now i see strange situation as for me. Ntpd reads data from SHM if my binary launched and update output

[root@*****]# ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*SHM(0)          .GPS.            0 l    5   16  377    0.000   19.906   8.438

 

[root@*****]# ntpq -c readvar
associd=0 status=0415 leap_none, sync_uhf_radio, 1 event, clock_sync,
version="ntpd 4.2.6p5@1.2349 Tue Feb 18 06:29:31 UTC 2014 (1)",
processor="i686", system="Linux/4.4.135-std-pae-alt1", leap=00,
stratum=1, precision=-23, rootdelay=0.000, rootdisp=30.456, refid=GPS,
reftime=e2839b77.23f81fef  Thu, Jun  4 2020 19:10:31.140,
clock=e2839b77.ff8798c2  Thu, Jun  4 2020 19:10:31.998, peer=20962, tc=4,
mintc=3, offset=19.906, frequency=-40.233, sys_jitter=8.438,
clk_jitter=6.504, clk_wander=0.311
 

 

but i can’t understand. My logs have Thu, Jun  4 2020 14:00 — 14.30 events.

But ntpd eats logs and output real time 19:10. 

 

Maybe i should write anything else to SHM or change some fileds to break ntp

 

 

--
артур хайруллин