Again, this requires the network to be up? I use timedatectl to set my timezone, will look more into it. Could be all is rolled together... On 09/01/2015 01:35 PM, Nicolas Repentin wrote: > > Don't know.. I saw this on the web > > > Centos 7 use systemd. I suggest you use it. > > Use the command timedatectl > <http://www.freedesktop.org/software/systemd/man/timedatectl.html> > > Enable network time synchronization: > > timedatectl set-ntp True > > > > > Create a conf file: > > vi /etc/systemd/timesyncd.conf > > > > > with content like this: > > [Time] > > NTP= yourserver.org > > > > > Start systemd-timedated service: > > systemctl start systemd-timedated > > > > > > > Nicolas Repentin > > <nicolas at shivaserv.fr> > > --------- Original Message --------- > *From*: Robert Moskowitz > *To*: Conversations around CentOS on ARM hardware > *Date*: Tue Sep 01 19:26:49 GMT+02:00 2015 > *Subject*: Re: [Arm-dev] Re: System time > > > On 09/01/2015 01:15 PM, Nicolas Repentin wrote: >> >> >> Oh, I did know about systemd-timesyncd, need to check about it :-) >> > > Can't find it in the repo, what provides it? > > >> >> >> >> Nicolas Repentin >> >> <nicolas at shivaserv.fr> >> >> --------- Original Message --------- >> *From*: Robert Moskowitz >> *To*: Conversations around CentOS on ARM hardware >> *Date*: Tue Sep 01 19:04:38 GMT+02:00 2015 >> *Subject*: Re: [Arm-dev] System time >> >> >> 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 at 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 at centos.org >>>> https://lists.centos.org/mailman/listinfo/arm-dev >>> >>> >>> _______________________________________________ >>> Arm-dev mailing list >>> Arm-dev at centos.org >>> https://lists.centos.org/mailman/listinfo/arm-dev >> >> _______________________________________________ >> Arm-dev mailing list >> Arm-dev at centos.org >> https://lists.centos.org/mailman/listinfo/arm-dev >> >> >> _______________________________________________ >> Arm-dev mailing list >> Arm-dev at centos.org >> https://lists.centos.org/mailman/listinfo/arm-dev > > _______________________________________________ > Arm-dev mailing list > Arm-dev at centos.org > https://lists.centos.org/mailman/listinfo/arm-dev > > > _______________________________________________ > Arm-dev mailing list > Arm-dev at centos.org > https://lists.centos.org/mailman/listinfo/arm-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/arm-dev/attachments/20150901/2d356a0f/attachment-0006.html>