From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][PATCH v2 2/2] ntp: make servers configurable and default to none configured
Date: Thu, 22 Nov 2012 17:05:29 +0000 [thread overview]
Message-ID: <4785971.dXgzFbP6o7@helios> (raw)
In-Reply-To: <7c3ea4dccee800720d34bbc4aa81e297e6c4ebab.1353602922.git.paul.eggleton@linux.intel.com>
On Thursday 22 November 2012 16:49:35 Paul Eggleton wrote:
> People can't blindly use pool.ntp.org, especially if they are building
> for a product or something that could be used in a product, so at least
> try to get people to do the right thing and not use pool.ntp.org by
> default.
>
> The previous network interface up script is now installed as
> ntpdate-sync in ${bindir} (and symlinked as the network if-up script).
> NTPSERVERS needs to be set in /etc/default/ntpdate.default at runtime,
Martin points out that should be "/etc/default/ntpdate" not
"/etc/default/ntpdate.default" - I have fixed the commit message on the branch.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-11-22 17:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 16:49 [meta-networking][PATCH v2 0/2] ntp fixes Paul Eggleton
2012-11-22 16:49 ` [meta-networking][PATCH v2 1/2] ntp: cleanup recipes and fix SSL support Paul Eggleton
2012-12-04 7:44 ` [danny?] " Anders Darander
2012-12-04 9:21 ` Paul Eggleton
2012-12-04 11:20 ` Burton, Ross
2012-12-04 11:21 ` Burton, Ross
2012-12-04 11:56 ` Martin Jansa
2012-11-22 16:49 ` [meta-networking][PATCH v2 2/2] ntp: make servers configurable and default to none configured Paul Eggleton
2012-11-22 17:05 ` Paul Eggleton [this message]
2012-11-26 16:28 ` [meta-networking][PATCH v2 0/2] ntp fixes Martin Jansa
2012-11-27 19:40 ` Joe MacDonald
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=4785971.dXgzFbP6o7@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.