<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Problem is an 'old' ver of chrony:<br>
<br>
<div class="moz-cite-prefix">On 09/02/2015 11:01 AM, Robert
Moskowitz wrote:<br>
</div>
<blockquote cite="mid:55E70F62.1060304@htt-consult.com" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
This is not working on a new mSD with only chrony installed and
the changes listed below.<br>
<br>
It works on F22 'out of the box' with these changes.<br>
</blockquote>
<br>
From the Fedora-arm list:<br>
<br>
=======<br>
<br>
<div class="moz-cite-prefix">On 09/02/2015 11:41 AM, Miroslav
Lichvar wrote:<br>
</div>
<blockquote cite="mid:20150902154114.GC29274@localhost" type="cite">In
RHEL7 is currently chrony-1.29 which doesn't have the no RTC
fallback with the -s option. You might want to wait for 7.2, which
likely will have chrony-2.1.1.
</blockquote>
=======<br>
<br>
<blockquote cite="mid:55E70F62.1060304@htt-consult.com" type="cite">
Got to get this working...<br>
</blockquote>
<br>
So can we have chrony-2.1.1 ??? Please :)<br>
<br>
<blockquote cite="mid:55E70F62.1060304@htt-consult.com" type="cite">
<br>
<div class="moz-cite-prefix">On 09/02/2015 08:56 AM, Robert
Moskowitz wrote:<br>
</div>
<blockquote cite="mid:55E6F21A.1090805@htt-consult.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
On the Fedora-arm list I learned that chronyd and
systemd-timesyncd conflict. F22 is using chronyd with
systemd-timesyncd not enabled. To get chronyd to set the system
time based on the last boot you need:<br>
<br>
In /etc/sysconfig/chronyd<br>
OPTIONS="-s"<br>
<br>
and /etc/chrony.conf<br>
#rtcsync<br>
rtcdevice /dev/nonexist<br>
<br>
shortly after boot if no network connection, your system time is
set to the last content in /var/lib/chrony/drift<br>
<br>
So please add chronyd to the minimal install and set it with
these 'defaults', or provide an easy way to configure for 'no
rtc'.<br>
<br>
<div class="moz-cite-prefix">On 09/01/2015 11:29 PM, Robert
Moskowitz wrote:<br>
</div>
<blockquote cite="mid:55E66D28.7010101@htt-consult.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
The archlinux wiki says this should work at boot even without
a network connection but it is not. Perhaps there is some
extra steps to set this up right?<br>
<br>
If not, is this a bug? Not supprising that the Intel based
testing did not see this, as how many Intel boxes do not have
an rtc? Only those with dead batteries...<br>
<br>
<div class="moz-cite-prefix">On 09/01/2015 01:46 PM, Robert
Moskowitz wrote:<br>
</div>
<blockquote cite="mid:55E5E482.9070108@htt-consult.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
I just did a test, as timedatectl indicates that ntp is on.
It did not set the time on reboot. It is not doing that
auto stuff mentioned in the description. :(<br>
<br>
<div class="moz-cite-prefix">On 09/01/2015 01:39 PM, Robert
Moskowitz wrote:<br>
</div>
<blockquote cite="mid:55E5E2D8.1050103@htt-consult.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
Oh, I should have read further down the page of: <a
moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://wiki.archlinux.org/index.php/Systemd-timesyncd"><a class="moz-txt-link-freetext" href="https://wiki.archlinux.org/index.php/Systemd-timesyncd">https://wiki.archlinux.org/index.php/Systemd-timesyncd</a></a><br>
<br>
....<br>
<br>
<div class="moz-cite-prefix">On 09/01/2015 01:38 PM,
Robert Moskowitz wrote:<br>
</div>
<blockquote cite="mid:55E5E27C.4090008@htt-consult.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
Again, this requires the network to be up?<br>
<br>
I use timedatectl to set my timezone, will look more
into it. Could be all is rolled together...<br>
<br>
<div class="moz-cite-prefix">On 09/01/2015 01:35 PM,
Nicolas Repentin wrote:<br>
</div>
<blockquote
cite="mid:786737858.2.1441128911297.JavaMail.nicolas@shivaserv.fr"
type="cite">
<p>Don't know.. I saw this on the web<br>
<br>
<br>
</p>
<p>Centos 7 use systemd. I suggest you use it.<br>
<br>
</p>
<p>Use the command <a moz-do-not-send="true"
href="http://www.freedesktop.org/software/systemd/man/timedatectl.html">timedatectl</a><br>
<br>
</p>
<p>Enable network time synchronization:<br>
<br>
</p>
<p>timedatectl set-ntp True<br>
</p>
<p><br>
<br>
</p>
<p><br>
</p>
<p>Create a conf file:<br>
<br>
</p>
<p>vi /etc/systemd/timesyncd.conf<br>
</p>
<p><br>
<br>
</p>
<p><br>
</p>
<p>with content like this:<br>
<br>
</p>
<p>[Time]<br>
<br>
</p>
<p>NTP= yourserver.org<br>
</p>
<p><br>
<br>
</p>
<p><br>
</p>
<p>Start systemd-timedated service:<br>
<br>
</p>
<p>systemctl start systemd-timedated<br>
</p>
<p><br>
<br>
</p>
<p><br>
<br>
<br>
</p>
<p>Nicolas Repentin<br>
</p>
<p><a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:nicolas@shivaserv.fr"><nicolas@shivaserv.fr></a><br>
<br>
</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:26:49 GMT+02:00
2015<br>
<b>Subject</b>: Re: [Arm-dev] Re: System time<br>
</arm-dev@centos.org></rgm@htt-consult.com></div>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<br>
<br>
<div class="moz-cite-prefix">On 09/01/2015 01:15 PM,
Nicolas Repentin wrote:<br>
</div>
<blockquote
cite="mid:625033636.2.1441127759342.JavaMail.nicolas@shivaserv.fr"
type="cite">
<p><br>
</p>
<p>Oh, I did know about systemd-timesyncd, need to
check about it :-)<br>
</p>
</blockquote>
<br>
Can't find it in the repo, what provides it?<br>
<br>
<br>
<blockquote
cite="mid:625033636.2.1441127759342.JavaMail.nicolas@shivaserv.fr"
type="cite">
<p><br>
<br>
<br>
</p>
<p>Nicolas Repentin<br>
</p>
<p><a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:nicolas@shivaserv.fr"><nicolas@shivaserv.fr></a><br>
<br>
</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>
</arm-dev@centos.org></rgm@htt-consult.com></div>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<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 moz-do-not-send="true"
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 moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:Arm-dev@centos.org">Arm-dev@centos.org</a>
<br>
<a moz-do-not-send="true"
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 moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Arm-dev@centos.org">Arm-dev@centos.org</a>
<a moz-do-not-send="true" 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>
_______________________________________________<br>
Arm-dev mailing list<br>
<a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:Arm-dev@centos.org">Arm-dev@centos.org</a><br>
<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://lists.centos.org/mailman/listinfo/arm-dev">https://lists.centos.org/mailman/listinfo/arm-dev</a><br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Arm-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Arm-dev@centos.org">Arm-dev@centos.org</a>
<a moz-do-not-send="true" 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>
_______________________________________________<br>
Arm-dev mailing list<br>
<a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:Arm-dev@centos.org">Arm-dev@centos.org</a><br>
<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://lists.centos.org/mailman/listinfo/arm-dev">https://lists.centos.org/mailman/listinfo/arm-dev</a><br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Arm-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Arm-dev@centos.org">Arm-dev@centos.org</a>
<a moz-do-not-send="true" 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>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Arm-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Arm-dev@centos.org">Arm-dev@centos.org</a>
<a moz-do-not-send="true" 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>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Arm-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Arm-dev@centos.org">Arm-dev@centos.org</a>
<a moz-do-not-send="true" 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>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Arm-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Arm-dev@centos.org">Arm-dev@centos.org</a>
<a moz-do-not-send="true" 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>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Arm-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Arm-dev@centos.org">Arm-dev@centos.org</a>
<a moz-do-not-send="true" 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>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Arm-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Arm-dev@centos.org">Arm-dev@centos.org</a>
<a moz-do-not-send="true" 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>
<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>