Difference between revisions of "NTP"

From Openembedded.org
Jump to: navigation, search
 
Line 11: Line 11:
 
</blockquote>
 
</blockquote>
  
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.
+
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. To do this, use a bbappend for the ntp recipe in your own layer providing ntp.conf and/or ntpdate.default with the appropriate servers set within.

Latest revision as of 17:10, 22 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. To do this, use a bbappend for the ntp recipe in your own layer providing ntp.conf and/or ntpdate.default with the appropriate servers set within.

Personal tools
Namespaces

Variants
Actions
Navigation
Categories
OE services
Toolbox