The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.
Difference between revisions of "Package:Chrony"
Threesixes (talk | contribs) m (Threesixes moved page Set Up Chrony For Accurate System Time to Package:Chrony: 4 the chaos) |
Threesixes (talk | contribs) m (update console templates & insert ebuild info) |
||
| Line 1: | Line 1: | ||
{{Ebuild | |||
|Summary=Chrony is a pair of programs (chronyd and chronyc) which are used to maintain the accuracy of the system clock on a computer. chronyd has been specifically written to work well for systems which have only an intermittent (e.g. dial-up) connection to the network where the NTP servers are. It still works well in a "permanently connected" mode. | |||
|CatPkg=net-misc/chrony | |||
|Homepage=http://chrony.tuxfamily.org/ | |||
}} | |||
=== Accurate System Time (NTP) === | === Accurate System Time (NTP) === | ||
| Line 5: | Line 11: | ||
The recommended NTP client/server is '''{{Package|net-misc/chrony}}'''. | The recommended NTP client/server is '''{{Package|net-misc/chrony}}'''. | ||
{{console|body= | |||
###i## emerge chrony | ###i## emerge chrony | ||
###i## rc-update add chronyd default | ###i## rc-update add chronyd default | ||
}} | |||
Use something like the following for your <code>/etc/chrony/chrony.conf</code>: | Use something like the following for your <code>/etc/chrony/chrony.conf</code>: | ||
| Line 33: | Line 39: | ||
Chronyd can then be started immediately by running <code>rc</code> to start all new services: | Chronyd can then be started immediately by running <code>rc</code> to start all new services: | ||
{{console|body= | |||
###i## rc | ###i## 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 <code>dhcpcd</code>, add the following to <code>/etc/conf.d/chronyd</code>: | 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 <code>dhcpcd</code>, add the following to <code>/etc/conf.d/chronyd</code>: | ||
| Line 47: | Line 53: | ||
[[Category:System]] | [[Category:System]] | ||
[[Category:Official Documentation]] | [[Category:Official Documentation]] | ||
{{EbuildFooter}} | |||
Revision as of 03:32, January 25, 2015
Chrony
We welcome improvements to this page. To edit this page, Create a Funtoo account. Then log in and then click here to edit this page. See our editing guidelines to becoming a wiki-editing pro.
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 net-misc/chrony.
root # emerge chrony root # rc-update add chronyd default
Use something like the following for your /etc/chrony/chrony.conf:
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 me@emailprovider.com 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:
root # 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 /etc/conf.d/chronyd:
rc_need=dhcpcd
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.