Error on g suffix in time1 fudge

[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)
-- 
Sanjeev Gupta
+65 98551208     http://www.linkedin.com/in/ghane


On Sat, Aug 17, 2019 at 5:04 AM Eric S. Raymond <esr at thyrsus.com> wrote:

> Sanjeev Gupta <ghane0 at gmail.com>:
> > Eric,
> >
> > My (minimal) config:
> >
> > root at 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 day link
> > filegen rawstats   type day link
> > filegen sysstats   type day link
> > driftfile /var/lib/ntp/ntp.drift
> > statistics loopstats peerstats clockstats
> > refclock shm unit 0 refid GPS time1 0.650g flag4 1 # minpoll 1 maxpoll 5
> > restrict -4 default kod nomodify nopeer noquery limited
> > restrict -6 default kod nomodify nopeer noquery limited
> > restrict 127.0.0.1
> > restrict ::1
> > restrict source nomodify noquery
> >
> >
> > ntpd command line:
> >
> > root at ntpmon:~/ntpsec/docs# kill -9 `pidof ntpd` ; ntpd -D 100000
> >
> > Log file:
> > 2019-08-17T04:38:01 ntpd[22651]: INIT: Using SO_TIMESTAMPNS
> > 2019-08-17T04:38:01 ntpd[22651]: IO: Listen and drop on 0 v6wildcard
> > [::]:123
> > 2019-08-17T04:38:01 ntpd[22651]: IO: Listen and drop on 1 v4wildcard
> > 0.0.0.0:123
> > 2019-08-17T04:38:01 ntpd[22651]: IO: Listen normally on 2 lo
> 127.0.0.1:123
> > 2019-08-17T04:38:01 ntpd[22651]: IO: Listen normally on 3 eth1
> > 203.123.48.219:123
> > 2019-08-17T04:38:01 ntpd[22651]: IO: Listen normally on 4 lo [::1]:123
> > 2019-08-17T04:38:01 ntpd[22651]: IO: Listen normally on 5 eth1
> > [2405:fc00:0:1::123]:123
> > 2019-08-17T04:38:01 ntpd[22651]: IO: Listen normally on 6 eth1
> > [fe80::204:23ff:feb8:1c1e%3]:123
> > 2019-08-17T04:38:01 ntpd[22651]: IO: Listening on routing socket on fd
> #23
> > for interface updates
> > 2019-08-17T04:38:01 ntpd[22651]: INIT: This system has a 32-bit time_t.
> > 2019-08-17T04:38:01 ntpd[22651]: INIT: This ntpd will fail on
> > 2038-01-19T03:14:07Z.
> > 2019-08-17T04:38:01 ntpd[22651]: PROTO: 0.0.0.0 c01d 0d kern kernel time
> > sync enabled
> > 2019-08-17T04:38:01 ntpd[22651]: PROTO: 0.0.0.0 c012 02 freq_set kernel
> > 39.594910 PPM
> > 2019-08-17T04:38:01 ntpd[22651]: PROTO: 0.0.0.0 c016 06 restart
> > 2019-08-17T04:38:01 ntpd[22651]: NTSc: Using system default root
> > certificates.
> >
> >
> > root at ntpmon:~/ntpsec/docs# ntpq -V
> > ntpq ntpsec-1.1.6+ 2019-08-16T20:21:12Z (git rev f99a58821)
> > root at ntpmon:~/ntpsec/docs# ntpq -pn
> > server=localhost No association IDs returned
> >
> > --
> > Sanjeev Gupta
> > +65 98551208     http://www.linkedin.com/in/ghane
> >
> >
> > On Sat, Aug 17, 2019 at 3:50 AM Eric S. Raymond via devel <
> devel at ntpsec.org>
> > wrote:
> >
> > > Sanjeev, would you please look in your logs and see if the config
> > > parser throws an error related to that line?
> > > --
> > >                 <a href="http://www.catb.org/~esr/">Eric S.
> Raymond</a>
> > >
> > > You know why there's a Second Amendment?  In case the government fails
> to
> > > follow the first one.
> > >          -- Rush Limbaugh, in a moment of unaccustomed profundity 17
> Aug
> > > 1993
>
> Odd that it's not throwing a parse error.
>
> Looks like I'll have to build some test jigs to get to the bottom of this.
> --
>                 <a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/devel/attachments/20190817/41a5da04/attachment.htm>