Re: [chrony-users] Not getting time from gpsd

2016-08-06 Thread Steve Horton
I'd look closer at the SOCK option under the refclock section. https://chrony.tuxfamily.org/manual.html#refclock-directive On Aug 6, 2016 12:00 AM, "Chris Greenman" wrote: > > Hello, > I'm having an issue with getting time from gpsd. > > My setup is: > Raspberry Pi 3 running Jessie Lite > USB

Re: [chrony-users] Not getting time from gpsd

2016-08-06 Thread Steve Horton
10 AM, "Chris Greenman" wrote: > Same thing. Already tried it. > > On Aug 6, 2016 6:35 AM, "Steve Horton" wrote: > >> I'd look closer at the SOCK option under the refclock section. >> https://chrony.tuxfamily.org/manual.html#refclock-directive >

Re: [chrony-users] Not getting time from gpsd

2016-08-06 Thread Steve Horton
y _|___ Advanced Research _| Fax: +1(604)822-5324 > UBC, Vancouver,BC _|_ Program in Cosmology | un...@physics.ubc.ca > Canada V6T 1Z1 | and Gravity __|_ www.theory.physics.ubc.ca/ > > On Sat, 6 Aug 2016, Steve Horton wrote: > > >> Not really Chris. I don&#

Re: [chrony-users] Not getting time from gpsd

2016-08-06 Thread Steve Horton
> > # set larger delay to allow the NMEA source to overlap with > # the other sources and avoid the falseticker status > refclock SHM 0 refid GPS precision 1e-1 offset 0. delay 0.2 > #refclock SHM 1 refid PPS precision 1e-9 > refclock SOCK /var/run/chrony.ttyACM0.sock refid GPSS &

Re: [chrony-users] Not getting time from gpsd

2016-08-06 Thread Steve Horton
rep > gpsd 31426 1 0 13:36 ?00:00:00 /usr/sbin/gpsd -N -F > /var/run/chrony.ttyACM0.sock /dev/ttyACM0 > > cgps shows 3d fix > > On Sat, Aug 6, 2016 at 2:11 PM, Steve Horton > wrote: > >> Ok..can I see your gpsd conf? >> >> On Aug 6, 2016 1:3

Re: [chrony-users] Not getting time from gpsd

2016-08-07 Thread Steve Horton
gt; [ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME" > do_stop > case "$?" in > 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;; > 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;; > esac > ;;

Re: [chrony-users] Not getting time from gpsd

2016-08-08 Thread Steve Horton
mmands I used were: > > root@IrishMistII:/tmp# strace -o /tmp/chrony.strace.out chronyd > root@IrishMistII:/tmp# strace -o /tmp/gpsd.strace.out gpsd -D 8 -F > /var/run/chrony.ttyACM0.sock /dev/ttyACM0 > > On Aug 7, 2016 12:50 AM, "Steve Horton" wrote: > >> We need to see

Re: [chrony-users] Not getting time from gpsd

2016-08-08 Thread Steve Horton
Awesome man I'm glad it's working for you! I use buildroot for most everything and then I can compile everything much easier all at once On Aug 8, 2016 1:22 PM, "Chris Greenman" wrote: > UGH!!!I really wish distros would provide software that is more up to > date.Looks like it might have

Re: [chrony-users] Getting chrony status

2016-08-06 Thread Steve Horton
Chronyc tracking -will show how "off" you are from the time of your servers UTC. I usually set my clocks in the bios to utc, or very close and chrony will use this as a starting point after boot. On Aug 6, 2016 12:11 PM, "Mauro Condarelli" wrote: > Hi, > I need to start an application with stabl

Re: [chrony-users] Getting chrony status

2016-08-06 Thread Steve Horton
t; > System time : 0.08512 seconds fast of NTP time > > Last offset : -0.000437271 seconds > > RMS offset : 0.000437271 seconds > > Frequency : 6.202 ppm slow > > Residual freq : -7.681 ppm > > Skew: 0.040 ppm > > Root delay