From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ntpd problem: randomly refusing/dropping client requests
Date: Wed, 5 Jul 2006 19:32:09 -0700 [thread overview]
Message-ID: <7573e9640607051932p4e68293dy85c349df093a5af6@mail.gmail.com> (raw)
In-Reply-To: <20060706013319.GA6810@nibiru.local>
On 7/5/06, Enrico Weigelt <weigelt@metux.de> wrote:
>
> Hi folks,
>
> I've got an problem w/ ntpd: syncing w/ ntpdate against it
> fails from time to time. Sometimes just for a few minutes,
> sometimes longer.
>
> I know it will call itself stratum 16 (which is dropped by ntpdate)
> if it hasn't synchronized to a proper reference clock yet, so it
> will take some time after startup until its usable.
>
> But why are there such problems once ntp has been sychronized ?
I'm not an ntpd expert by any means, but maybe you could post your config files?
Also, have you read http://www.eecis.udel.edu/~mills/ntp/html/debug.html?
-Richard
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2006-07-06 2:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 1:33 [gentoo-user] ntpd problem: randomly refusing/dropping client requests Enrico Weigelt
2006-07-06 2:32 ` Richard Fish [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7573e9640607051932p4e68293dy85c349df093a5af6@mail.gmail.com \
--to=bigfish@asmallpond.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox