Yo Hal!
On Tue, 30 Aug 2016 23:24:26 -0700
Hal Murray wrote:
> > Hm. I think I get it - and you've just added a pretty powerful
> > reason to eventually pull the refclocks into a separate daemon by
> > telling me I need to get ntpd itself out of the PPS-watching
> > business entirely in order to
Yo Hal!
On Tue, 30 Aug 2016 22:56:43 -0700
Hal Murray wrote:
> g...@rellim.com said:
> > If you want to backup your graphs, just add a loggerd script to
> > gzip them to somewhere on a schedule.
>
> Wrong binding for "backup".
>
> The context was the way I'm currently looking at graphs. I
> Hm. I think I get it - and you've just added a pretty powerful reason to
> eventually pull the refclocks into a separate daemon by telling me I need to
> get ntpd itself out of the PPS-watching business entirely in order to get
> rid of that timer.
The reason I want to get rid of the every-sec
g...@rellim.com said:
> If you want to backup your graphs, just add a loggerd script to gzip them to
> somewhere on a schedule.
Wrong binding for "backup".
The context was the way I'm currently looking at graphs. I feed things like
this to gnuplot:
reset; load "foo1.gp"
pause -1
reset;
strom...@nexgo.de said:
> I have not yet managed to blind the GPS antenna completely, though, so I
> can't know what happens when it loses all signal.
Have you tried putting it under a metal pie tin?
Or inside a metal box? (being careful not to mangle the cord)
--
These are my opinions. I ha
g...@rellim.com said:
>> Most CPU chips include a temperature sensor.
> Which I have found does not correlate with any of my NTP data.
I have a Raspberry Pi sitting on a window sill. It gets a couple of hours of
late afternoon sun. There is a big temperature spike. Drift roughly follows
it.
Gary E. Miller writes:
> Most cheaper GPS always output PPS, even when they have no idea
> where they are or what time it is. Garmin documents this, as do others.
Well, the NavSpark mini does not output a PPS until it aquires a 3D
lock, as documented. The configuration program has options to eit
Hal Murray :
>
> e...@thyrsus.com said:
> > I'm not clear how we would tell if anything were broken. Or are you just
> > suggesting looking for a timing difference?
>
> Mostly I was suggesting that we needed to test it to make sure that it seemed
> to work rather than worrying about how well it
