Re: Error on g suffix in time1 fudge

2019-08-16 Thread Eric S. Raymond via devel
Sanjeev Gupta : > Eric,a data point. This works: > > refclock shm unit 0 refid GPS time1 619315200.450 flag4 1 > > (the large number is 1024 weeks, the 0.450 is a delay) That's good. Probably means there's a simple error in my asumtions about how parsing works. -- http://www.ca

Re: Error on g suffix in time1 fudge

2019-08-16 Thread Sanjeev Gupta via devel
Eric,a data point. This works: refclock shm unit 0 refid GPS time1 619315200.450 flag4 1 (the large number is 1024 weeks, the 0.450 is a delay) -- Sanjeev Gupta +65 98551208 http://www.linkedin.com/in/ghane On Sat, Aug 17, 2019 at 5:04 AM Eric S. Raymond wrote: > Sanjeev Gupta : > > Eri

Re: Error on g suffix in time1 fudge

2019-08-16 Thread Eric S. Raymond via devel
Sanjeev Gupta : > Eric, > > My (minimal) config: > > root@ntpmon:~/ntpsec/docs# grep -v "^#" /etc/ntp.conf | grep -v "^$" > logfile /var/www/html/ntp/ntpd.log > logconfig =syncall +clockall +peerall +sysall > statsdir /var/www/html/ntp/ > filegen loopstats type day link > filegen peerstats type

Re: Error on g suffix in time1 fudge

2019-08-16 Thread Sanjeev Gupta via devel
Eric, My (minimal) config: root@ntpmon:~/ntpsec/docs# grep -v "^#" /etc/ntp.conf | grep -v "^$" logfile /var/www/html/ntp/ntpd.log logconfig =syncall +clockall +peerall +sysall statsdir /var/www/html/ntp/ filegen loopstats type day link filegen peerstats type day link filegen protostats type da