Accurate System Time (NTP)
It's important that your Funtoo Linux system has an accurate clock. NTP (network time protocol) can ensure your clock is accurate at all time.
The recommended NTP client/server is Package:Chrony.
# emerge chrony
Chrony requires you set an upstream ntp server.
For broadband users:
# echo "server pool.ntp.org iburst" >> /etc/chrony/chrony.conf
For dial up or slow connections:
# echo "server pool.ntp.org offline" >> /etc/chrony/chrony.conf
Use something like the following for your
server time.apple.com maxupdateskew 100 driftfile /etc/chrony/chrony.drift keyfile /etc/chrony/chrony.keys commandkey 1 dumponexit dumpdir /var/log/chrony initstepslew 10 time.apple.com logdir /var/log/chrony log measurements statistics tracking logchange 0.5 mailonchange firstname.lastname@example.org 0.5 rtcfile /etc/chrony/chrony.rtc rtconutc sched_priority 1 lock_all
Chronyd can then be started immediately by running
rc to start all new services:
To test chronyd, set the time immediately, & exit:
# chronyd -q
To start the chronyd service:
# rc-update add chronyd default # rc
Because Funtoo Linux starts network daemons without waiting for an Internet connection to become available, and because chrony will attempt to synchronize the clock over the Internet when it first starts, you must manually configure chronyd to be dependent on whatever method you use to enable your outbound network connectivity. For example, if using
dhcpcd, add the following to
You should notice a marked improvement in your system clock's accuracy. If your system time was off by a significant amount,
chronyd will gradually correct your clock while the system runs.
To write your NTP sync time to the hardware at shutdown, and read hw clock at start.
# echo 'clock_hctosys="YES"' >> /etc/conf.d/hwclock # echo 'clock_systohc="YES"' >> /etc/conf.d/hwclock # rc-service hwclock restart # rc-update add hwclock boot