s. The commands 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" <stevejho
_msg 0
> fi
> ;;
> stop)
> [ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME"
> do_stop
> case "$?" in
> 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
> 2) [ "$VERBOSE" != no ] &am
7 02:57:32 2016
>
> 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
>
&
> $ ps -ef |grep gpsd |grep -v grep
> 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 <stevejhor...@gmail.com>
> wrote:
>
>>
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
y.ttyACM0.sock refid GPSS
>
> makestep 1 -1
>
>
>
>
> On Sat, Aug 6, 2016 at 10:41 AM, Steve Horton <stevejhor...@gmail.com>
> wrote:
>
>> Not really Chris. I don't see a sock option in your configuration file.
>> Gpsd should write time out to a device fil
ysics _|___ 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 do
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