Re: Refclock cleanup

2016-05-05 Thread Gary E. Miller
Yo Hal! On Thu, 05 May 2016 14:26:39 -0700 Hal Murray wrote: > g...@rellim.com said: > > gpsd can generate a huge amout of raw logging. Seeing the > > subsystem you want take hacks like this: > > gpsd -nND 9 /dev/ttyS0 |& egrep '(PPS|NTP}' > > I don't call that stuff "logging". It's de

Re: Refclock cleanup

2016-05-05 Thread Hal Murray
g...@rellim.com said: > gpsd can generate a huge amout of raw logging. Seeing the subsystem you > want take hacks like this: > gpsd -nND 9 /dev/ttyS0 |& egrep '(PPS|NTP}' I don't call that stuff "logging". It's debugging cruft. By logging, I mean stuff you can feed to gnuplot. Things l

Re: Refclock cleanup

2016-05-05 Thread Gary E. Miller
Yo Hal! On Thu, 05 May 2016 13:34:40 -0700 Hal Murray wrote: > I'm not sure I'd call it "cruft", but I'll be happy to use it as a > test case if/when we come up with the great refclock cleanup. Yes, reality can be a stern teacher. > > In the very lon

Refclock cleanup

2016-05-05 Thread Hal Murray
g...@rellim.com said: > I think we are mostly in agreement. Short term we need #20, long term it is > cruft. I'm not sure I'd call it "cruft", but I'll be happy to use it as a test case if/when we come up with the great refclock cleanup. > In the very l