<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/templates/timesyncd.conf.tmpl, branch rolling</title>
<subtitle> (mirror of https://github.com/vyos/vyos-cloud-init.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=rolling</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=rolling'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/'/>
<updated>2017-08-04T14:35:47+00:00</updated>
<entry>
<title>cc_ntp: fallback on timesyncd configuration if ntp is not installable</title>
<updated>2017-08-04T14:35:47+00:00</updated>
<author>
<name>Ryan Harper</name>
<email>ryan.harper@canonical.com</email>
</author>
<published>2017-08-01T23:00:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=5bba5db2655d88b8aba8fa06b30f8e91e2ca6836'/>
<id>urn:sha1:5bba5db2655d88b8aba8fa06b30f8e91e2ca6836</id>
<content type='text'>
Some systems like Ubuntu-Core do not provide an ntp package for
installation but do include systemd-timesyncd (an ntp client).
On such systems cloud-init will generate a timesyncd configuration
using the 'servers' and 'pools' values as ntp hosts for timesyncd to use.

LP: #1686485
</content>
</entry>
</feed>
