Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Dave Hart <davehart@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat-devel <bloat-devel@lists.bufferbloat.net>,
	bismark-devel@lists.bufferbloat.net,
	bismark-bootcamp@projectbismark.net
Subject: Re: smoketest #6 of cerowrt is go for testing
Date: Sat, 16 Jul 2011 04:05:19 +0000	[thread overview]
Message-ID: <CAMbSiYDp3A7LVp1yNaBZNTTe+OuzyMiGrGzBqNrd13dpgSUd+g@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6CaJ7LAF58HHXQt=tQd1DYXRrNUCrM-gd5JhTKJs0K8g@mail.gmail.com>

On Sat, Jul 16, 2011 at 02:40 UTC, Dave Taht <dave.taht@gmail.com> wrote:
> 0) We have a priority 3 issue with ntp starting up. NTP times out too early
> it keeps restarting, and restarting, and restarting... (it's on a 10 second
> timer) This is related to the dnssec issue I'm well aware of. It looks like
> 60 second timer would work better)

10 seconds is too small, but sometimes one minute might be too small a
timeout, too.  If possible, it may make sense to start ntpd, then
start time-step-tolerant daemons, then use the ntp-wait script to
block until ntpd's first clock sync, then start time-step-sensitive
daemons.

> (dnssec IS disabled by default in this build, so ntp isn't even needed
> and does eventually get the correct time if you kill off named.montime - and
> the right answer is to patch ntp to just issue the first queries for
>
> ntp -g option
>
> with the auth-needed bit off... I have NO idea how to do that with dnssec.

ntpd doesn't request dnssec verification -- it simply uses the
provided getaddrinfo().  Any tweaking of the resolver to avoid
requiring DNSSEC validation of queries will be outside the ntpd source
code.

Cheers,
Dave Hart

  reply	other threads:[~2011-07-16  3:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-16  2:40 Dave Taht
2011-07-16  4:05 ` Dave Hart [this message]
2011-07-17  0:02   ` Rick Jones
2011-07-17  4:35     ` Dave Hart
2011-07-17 12:34       ` Dave Taht
2011-07-17 15:50         ` Fwd: " Dave Hart
2011-07-17 20:40           ` Evan Hunt
2011-07-18 17:40       ` Rick Jones
2011-07-17  0:01 ` Rick Jones

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=CAMbSiYDp3A7LVp1yNaBZNTTe+OuzyMiGrGzBqNrd13dpgSUd+g@mail.gmail.com \
    --to=davehart@gmail.com \
    --cc=bismark-bootcamp@projectbismark.net \
    --cc=bismark-devel@lists.bufferbloat.net \
    --cc=bloat-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=davehart_gmail_exchange_tee@davehart.net \
    /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