Thanks. I already enabled my NTP sources and you're right, the gps is getting marked as bad. I'll play with that today.
Chris On Aug 9, 2016 4:42 AM, "Miroslav Lichvar" <mlich...@redhat.com> wrote: > On Mon, Aug 08, 2016 at 01:21:56PM -0400, Chris Greenman wrote: > > 210 Number of sources = 1 > > MS Name/IP address Stratum Poll Reach LastRx Last sample > > > > ============================================================ > =================== > > #* GPS 0 4 377 17 +296us[ +347us] +/- > > 200ms > > > > > > I am perfectly happy with 200ms error in time. That more than suits my > > needs. > > You might want to try this with some NTP sources and see how accurate > is the GPS time source. From that you would adjust the offset value on > the refclock SHM line so the the error is reduced and the GPS source > is not marked as a falseticker when there are other source. I'd also > suggest to add "minsamples 64" to the refclock directive, so chronyd > doesn't try to follow short-term variations in the measured offset > (the error in the message based GPS time tends to be non-random). > > -- > 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. > >
