On Tue, Nov 8, 2011 at 7:27 PM, Dave Hart wrote:
>
> On Wed, Nov 9, 2011 at 03:12, Nathan Kitchen
> wrote:
> > On Tue, Nov 8, 2011 at 6:59 PM, Dave Hart wrote:
> >> I agree that I would not expect to see any difference in behavior
> >> between LAN source only
On Tue, Nov 8, 2011 at 6:59 PM, Dave Hart wrote:
>
> On Fri, Nov 4, 2011 at 23:27, Nathan Kitchen
> wrote:
> > I'm curious about some behavior that I'm observing on a host running
> > ntpd as a client. As I understand it, configuring a local reference
> >
On Sun, Nov 6, 2011 at 2:13 PM, Danny Mayer wrote:
> On 11/4/2011 7:27 PM, Nathan Kitchen wrote:
> > I'm curious about some behavior that I'm observing on a host running
> > ntpd as a client. As I understand it, configuring a local reference
> > clock--either
> ntpq -crv
associd=0 status=0515 leap_none, sync_local, 1 event, clock_sync,
version="ntpd 4.2.6p1@1.2158-o Thu Sep 29 06:24:01 UTC 2011 (2)",
processor="x86_64", system="Linux/2.6.32.28",
leap=00, stratum=11, precision=-21, rootdelay=0.000, rootdisp=11.927,
refid=LOCAL(0), reftime=d262b12c.93e52
I'm curious about some behavior that I'm observing on a host running
ntpd as a client. As I understand it, configuring a local reference
clock--either an undisciplined local clock or orphan mode--shouldn't
help me, but I see different behavior when I do have one. In
particular, when I'm synchronizi
