<p><p><br></p><p>Oh, I did know about systemd-timesyncd, need to check about it :-)<br><br><br><br></p><p>Nicolas Repentin<br></p><p><nicolas@shivaserv.fr><br><br></p><p></p></p><div class='dm__nested'><div class='dm__nested_header'>--------- Original Message ---------<br>
<b>From</b>: Robert Moskowitz <rgm@htt-consult.com><br>
<b>To</b>: Conversations around CentOS on ARM hardware <arm-dev@centos.org><br>
<b>Date</b>: Tue Sep 01 19:04:38 GMT+02:00 2015<br>
<b>Subject</b>: Re: [Arm-dev] System time<br>
</div>
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">On 09/01/2015 12:16 PM, Nicolas wrote:<br>
</div>
<blockquote cite="mid:42c5b20b.1441124088412@shiva.shivaserv.fr"
type="cite">Hello<br>
<br>
I don't think any armv7 board like cubie has a battery to backup
clock<br>
I think ntpd is the only way, and seems to work well on my bpi
with c7. I will check if dns resolution works when date is 1970.<br>
<br>
I think setting the currenttime can be a good idea on the rbf tool
:-)</blockquote>
<br>
On the Fedora-arm list I was pointed to Systemd-timesyncd<br>
<br>
This does MOST of what I want. All that I think needs to be added
is for it to be enabled in the image and a initial date/time of the
image built date be there so the firstboot has a decent time.<br>
<br>
<blockquote cite="mid:42c5b20b.1441124088412@shiva.shivaserv.fr"
type="cite">
<div class="profimail-signature"><br>
Nicolas Repentin<br>
<a class="moz-txt-link-rfc2396E" href="mailto:nicolas@shivaserv.fr"><nicolas@shivaserv.fr></a></div>
<br>
<br>
<div class="profimail-cite-prefix">Le 1 septembre 2015 18:12,
Robert Moskowitz a écrit:<br>
</div>
<blockquote type="cite">How is system time set at boot? Is
ntpdate run after the network is
<br>
ready? How long does it retry waiting for the network to be
available?
<br>
<br>
I have seen a number of challenges becuase the system time is
back at
<br>
the epoch start as there is no battery rtc. And I wonder how
many
<br>
armv7 boards have a battery to maintain time across boots?
<br>
<br>
Minimally, a process could right the time, in the proper format,
to a
<br>
file, say /etc/currenttime every 5 min and at shutdown.
<br>
<br>
Then date can be run early in the boot process, piping this file
in. It
<br>
would not be perfect and does not help, much for new installs,
but
<br>
better than epoch start.
<br>
<br>
Plus /etc/currenttime can be at least set to the image build
date/time
<br>
so not even firstboot will be at epoch start.
<br>
<br>
Opinions?
<br>
<br>
<br>
_______________________________________________
<br>
Arm-dev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Arm-dev@centos.org">Arm-dev@centos.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.centos.org/mailman/listinfo/arm-dev">https://lists.centos.org/mailman/listinfo/arm-dev</a>
<br>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Arm-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Arm-dev@centos.org">Arm-dev@centos.org</a>
<a class="moz-txt-link-freetext" href="https://lists.centos.org/mailman/listinfo/arm-dev">https://lists.centos.org/mailman/listinfo/arm-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>
_______________________________________________<br>Arm-dev mailing list<br>Arm-dev@centos.org<br>https://lists.centos.org/mailman/listinfo/arm-dev<br></div>