On 09/01/2015 12:16 PM, Nicolas wrote:

Hello

I don't think any armv7 board like cubie has a battery to backup clock
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.

I think setting the currenttime can be a good idea on the rbf tool :-)

On the Fedora-arm list I was pointed to Systemd-timesyncd

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.

Nicolas Repentin
<nicolas@shivaserv.fr>

Le 1 septembre 2015 18:12, Robert Moskowitz a écrit:

How is system time set at boot? Is ntpdate run after the network is
ready? How long does it retry waiting for the network to be available?

I have seen a number of challenges becuase the system time is back at
the epoch start as there is no battery rtc. And I wonder how many
armv7 boards have a battery to maintain time across boots?

Minimally, a process could right the time, in the proper format, to a
file, say /etc/currenttime every 5 min and at shutdown.

Then date can be run early in the boot process, piping this file in. It
would not be perfect and does not help, much for new installs, but
better than epoch start.

Plus /etc/currenttime can be at least set to the image build date/time
so not even firstboot will be at epoch start.

Opinions?

_______________________________________________
Arm-dev mailing list
Arm-dev@centos.org
https://lists.centos.org/mailman/listinfo/arm-dev
_______________________________________________
Arm-dev mailing list
Arm-dev@centos.org
https://lists.centos.org/mailman/listinfo/arm-dev