[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gpsd-dev] Clarifications needed for the time-service HOWTO
From: |
Eric S. Raymond |
Subject: |
Re: [gpsd-dev] Clarifications needed for the time-service HOWTO |
Date: |
Thu, 24 Oct 2013 08:10:58 -0400 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Miroslav Lichvar <address@hidden>:
> > By using a large offset we basically tell ntpd to ignore it unless it is
> > the last resort. noselect prevents that ultimate fallback.
>
> But do you really want that fallback? If the clock was well
> synchronized, letting it drift is usually a better option than
> switching to a NMEA source, let alone one with purposely wrong fudge.
>
> Also, it increases the chance that it will with another bad source
> outvote a good source.
I think Miroslav has a good argument here, Gary. I won't change your
language substantively wutout your say-so, but I think you should
consider doing so.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
Re: [gpsd-dev] Clarifications needed for the time-service HOWTO, Gary E. Miller, 2013/10/23
Re: [gpsd-dev] Clarifications needed for the time-service HOWTO, Miroslav Lichvar, 2013/10/24
Re: [gpsd-dev] Clarifications needed for the time-service HOWTO,
Eric S. Raymond <=
Re: [gpsd-dev] Clarifications needed for the time-service HOWTO, Gary E. Miller, 2013/10/24
Re: [gpsd-dev] Clarifications needed for the time-service HOWTO, Eric S. Raymond, 2013/10/24
Re: [gpsd-dev] Clarifications needed for the time-service HOWTO, Gary E. Miller, 2013/10/24
Re: [gpsd-dev] Clarifications needed for the time-service HOWTO, Hal Murray, 2013/10/24