Re: -g broken

Yo Hal! On Fri, 23 Mar 2018 17:15:51 -0700 Hal Murray via devel wrote: > Gary said: > > The raspberry pi has no RTC. When it starts cold, the time may > > well be in 1969. Somehow, not sure how, that becomes 2134. Then > > gpsd uses that as the GPS epoch, and things go

Re: -g broken

Gary said: > The raspberry pi has no RTC. When it starts cold, the time may well be in > 1969. Somehow, not sure how, that becomes 2134. Then gpsd uses that as the > GPS epoch, and things go downhill from there... So gpsd does something stupid and you expect ntpd to figure out how to

Re: -g broken

Yo Hal! On Fri, 23 Mar 2018 14:52:31 -0700 Hal Murray via devel wrote: > > I want my clock not stuck in 2134. -g alone does not fix that. > > Back to the beginning. Where does 2134 come from? The raspberry pi has no RTC. When it starts cold, the time may well be in

Re: -g broken

> I want my clock not stuck in 2134. -g alone does not fix that. Back to the beginning. Where does 2134 come from? > 'tos minsane 3' fixes it, unless I'm offline, which is pretty common for > RasPi. If you are getting bogus time from a local source and you want to work offline, you are

Re: -g broken

>> I'm not sure the case you are describing. > Hangs, as in unresponsive, frozen. ntpmon fails to update its output. Is that a problem in ntpd or ntpmon? Try ntpq -p from another window and/or tail rawstats to see if it is getting any answers. > Seems to me any daemon that crashes itself on

Re: -g broken

Yo Hal! On Fri, 23 Mar 2018 13:34:53 -0700 Hal Murray via devel wrote: > Gary said: > >> It's a flag, not a variable. -g sets it. > > Yeah, and most daemons let you put flags in the config file. > > I'd be happy with a policy that said anything you can do on the >

Re: -g broken

Yo Hal! On Fri, 23 Mar 2018 13:45:02 -0700 Hal Murray via devel wrote: > Gary said: > > I guess I did not wait long enough. ntpd, and ntpmon, hang for > > about three minutes, then wake up fine. Hang is at: > > 2134-03-01T17:57:35 > > > How do we explain that? > > I'm

Re: -g broken

Gary said: > I guess I did not wait long enough. ntpd, and ntpmon, hang for about three > minutes, then wake up fine. Hang is at: 2134-03-01T17:57:35 > How do we explain that? I'm not sure the case you are describing. ntpd waits a while to be sure before stepping the clock. In general,

Re: -g broken

Gary said: >> It's a flag, not a variable. -g sets it. > Yeah, and most daemons let you put flags in the config file. I'd be happy with a policy that said anything you can do on the command line you can also do in the config file, but it doesn't seem like a big deal. [tinker doc for panic and

Re: -g broken

Yo Hal! On Thu, 22 Mar 2018 21:20:11 -0700 Hal Murray wrote: > Gary said: > > Also no way to put panicgate in the ntp.conf. At least the man > > page does not say how. > > It's a flag, not a variable. -g sets it. Yeah, and most daemons let you put flags in the

✘https://doc.ntpsec.org

Yo All! We have been serving the NTPsec docs at: https://docs.ntpsec.org I see someone started an https://doc.ntpsec.org on gitlab, but never got a valid cert on it. Can someone that knows how ntpsec/docs/wscipt works contact me so we can get the letsencrypt cert working? RGDS GARY