NTP: Difference between revisions

From Openembedded.org
Jump to navigation Jump to search
(Created page with "{| style="color:black; background-color:#ffcccc" width="100%" cellpadding="10" class="wikitable" |'''NOTE:''' This page is a work in progress.''' |} When building [http://suppor...")
 
No edit summary
Line 11: Line 11:
</blockquote>
</blockquote>


Once you have gone through the process of setting up / obtaining appropriate server address(es) - refer to the link above - you can use these in your OE configuration. With an upcoming change you can simply set the <code>NTP_SERVERS</code> variable in your distro configuration; for older versions you will need to modify/bbappend the ntp recipe and modify the configuration files as needed.
Once you have gone through the process of setting up / obtaining appropriate server address(es) - refer to the [http://www.pool.ntp.org/en/vendors.html pool.ntp.org vendor info page] - you can use these in your OE configuration. With an upcoming change you can simply set the <code>NTP_SERVERS</code> variable in your distro configuration; for older versions you will need to modify/bbappend the ntp recipe and modify the configuration files as needed.

Revision as of 14:31, 21 November 2012

NOTE: This page is a work in progress.

When building ntp for use within an image produced from OpenEmbedded there is an important concern with regard to setting the default server(s) used for time synchronisation.

From http://www.pool.ntp.org/en/vendors.html:

You must absolutely not use the default pool.ntp.org zone names as the default configuration in your application or appliance.

Once you have gone through the process of setting up / obtaining appropriate server address(es) - refer to the pool.ntp.org vendor info page - you can use these in your OE configuration. With an upcoming change you can simply set the NTP_SERVERS variable in your distro configuration; for older versions you will need to modify/bbappend the ntp recipe and modify the configuration files as needed.