On 3/30/2012 03:30, David Lord wrote:
A C wrote:
On 3/29/2012 03:29, David Lord wrote:
Dave Hart wrote:
On Thu, Mar 29, 2012 at 02:44, A C agcarver+...@acarver.net wrote:
Without flag3 it appears that ntpd does the heavy lifting but is
unable to
use the PPS unless a prefer peer is set. With
On Sat, Mar 31, 2012 at 18:12, A C agcarver+...@acarver.net wrote:
I understand that the jitter will change but I'm talking about the minimum
possible jitter that ntpd can report for a given system. Using 4.2.6, the
minimum possible jitter reported (such as what is shown in the ntpq
billboard
A C wrote:
On 3/30/2012 03:30, David Lord wrote:
A C wrote:
On 3/29/2012 03:29, David Lord wrote:
Dave Hart wrote:
On Thu, Mar 29, 2012 at 02:44, A C agcarver+...@acarver.net wrote:
Without flag3 it appears that ntpd does the heavy lifting but is
unable to
use the PPS unless a prefer peer
I'm not sure which value you are referring to. From the
ntpq -p billboard over a day, I see values of jitter
of the GPS as low as 0.002
Yes, it's that jitter however there's a minimum computed value below
which it never goes (varies per system). On my system it used to be
computed at 0.061
A C wrote:
I'm not sure which value you are referring to. From the
ntpq -p billboard over a day, I see values of jitter
of the GPS as low as 0.002
Yes, it's that jitter however there's a minimum computed value below
which it never goes (varies per system). On my system it used to be
On 3/31/2012 20:19, David Lord wrote:
A C wrote:
I'm not sure which value you are referring to. From the
ntpq -p billboard over a day, I see values of jitter
of the GPS as low as 0.002
Yes, it's that jitter however there's a minimum computed value below
which it never goes (varies per
