From: john stultz <johnstul@us.ibm.com>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.30.1
Date: Tue, 7 Jul 2009 18:18:47 -0700 [thread overview]
Message-ID: <1f1b08da0907071818l1bae3256s30de304ed5ba3fa9@mail.gmail.com> (raw)
In-Reply-To: <200907050823.43743.gene.heskett@verizon.net>
On Sun, Jul 5, 2009 at 5:23 AM, Gene Heskett<gene.heskett@verizon.net> wrote:
> Just a heads up on 2.6.30.1, from logwatch's email:
>
> --------------------- XNTPD Begin ------------------------
>
>
> Time Reset 47 times (total: 11.411157 s average: 0.242791 s)
>
> Total synchronizations 74 (hosts: 4)
>
> ---------------------- XNTPD End -------------------------
> 2.6.30 didn't, with a lot more uptime, appear to need near as much support
> from the pool.ntp.org folks.
I don't see anything in the 2.6.30.1 patch that would effect NTP. Do
you have any peerstats/clockstats data? What does ntpdc -c peers and
ntpdc -c kerninfo show?
thanks
-john
prev parent reply other threads:[~2009-07-08 1:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-05 12:23 Gene Heskett
2009-07-08 1:18 ` john stultz [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=1f1b08da0907071818l1bae3256s30de304ed5ba3fa9@mail.gmail.com \
--to=johnstul@us.ibm.com \
--cc=gene.heskett@verizon.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®