[Arm-dev] Nit error in web instructions - Chronyd already installed

Robert Moskowitz

rgm at htt-consult.com
Mon Jan 23 15:45:29 UTC 2017


I just built a fresh CubieTruck install and booted it up (of course 
partitions on the HD, and only uboot on a 4Gb mSD card).

I did not log in right away, and when I did, I noticed the time was 
correct.  A check showed:

# systemctl status chronyd
● chronyd.service - NTP client/server
    Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; 
vendor preset: enabled)
    Active: active (running) since Thu 1970-01-01 00:00:24 UTC; 47 years 
0 months ago
   Process: 500 ExecStartPost=/usr/libexec/chrony-helper update-daemon 
(code=exited, status=0/SUCCESS)
   Process: 481 ExecStart=/usr/sbin/chronyd $OPTIONS (code=exited, 
status=0/SUCCESS)
  Main PID: 485 (chronyd)
    CGroup: /system.slice/chronyd.service
            └─485 /usr/sbin/chronyd

Jan 01 00:00:22 cubietruck systemd[1]: Starting NTP client/server...
Jan 01 00:00:23 cubietruck chronyd[485]: chronyd version 2.1.1 starting 
(+CM...)
Jan 01 00:00:23 cubietruck chronyd[485]: Generated key 1
Jan 01 00:00:24 cubietruck systemd[1]: Started NTP client/server.
Jan 01 00:00:46 cubietruck chronyd[485]: Selected source 108.59.2.24
Jan 01 00:00:46 cubietruck chronyd[485]: System clock wrong by 
1485185691.45...d
Jan 23 15:35:38 cubietruck chronyd[485]: System clock was stepped by 
1485185...s
Jan 23 15:35:45 cubietruck chronyd[485]: Selected source 45.56.123.24
Hint: Some lines were ellipsized, use -l to show in full.


So https://wiki.centos.org/SpecialInterestGroup/AltArch/Arm32

instructions to install chronyd is not needed.  It is already part of 
the base image.




More information about the Arm-dev mailing list