On Mon, Aug 08, 2016 at 09:05:03AM -0400, Chris Greenman wrote:
> I didn't think the -F option was correct but it didn't seem to work without
> it either.  I was just hunting and pecking.  My gps does not (directly)
> provide PPS.  It's a ublox 6 so I could probably wire it in but to be
> honest, I don't need that much precision.  For my needs NTP is accurate
> enough but it's not always available which is why I want time from GPS.

Note that GPS without PPS is typically less stable than NTP over
internet. Binary mode may work better than NMEA.

> As
> for the dependencies and starting order, that's easy to fix.  Right now
> gpsd is starting from init.d and chrony is starting from systemd.  I can
> just remove the rc#.d links and write a new .service file for gpsd with
> "After = chrony.service" and "Wanted by = default.target".  Then verify the
> chrony service file jives with the one for gpsd.

With SHM refclock that shouldn't be necessary. Only for SOCK chronyd
needs to be started first.

> The last gps strace I posted was with the -D 8 option specified.   I did
> not, however, specify -f to strace so it is not following after it forks.

The -N option disables forking. Another useful option is -n, which
tells gpsd to not wait for clients, so SHM is always updated.

> As soon as I get some play time today I'll run some new traces.  Is
> attaching the best way to send the files or is there a bit bucket somewhere
> I should use?

I think it's ok to post here if it's not too large (e.g. > 100KB). Or
you can compress it first.

-- 
Miroslav Lichvar

-- 
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org 
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org 
with "help" in the subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.

Reply via email to