| 1 |
On 29/08/2017 14:52, Stroller wrote: |
| 2 |
> Hello, |
| 3 |
> |
| 4 |
> Any recommendations for a simple NTP client? |
| 5 |
|
| 6 |
you asking for the simplest? |
| 7 |
|
| 8 |
ntpdate in a cron |
| 9 |
ntpdate in anacron (for latops and machines that are frequently off) |
| 10 |
|
| 11 |
|
| 12 |
ntp is designed for timeservers that by design do not make the clock |
| 13 |
jump around. Every second on the wall clock actually happens, none are |
| 14 |
missing. To do that, ntp adjusts the length of a second till the |
| 15 |
machine's time creeps up towards the real time as defined by the U.S |
| 16 |
Navy. Unless you are running software that is extremely time-critical |
| 17 |
(eg centralized auth servers, science experiments, etc) or you operate a |
| 18 |
proper time server, you absolutely do not need this behaviour ever.[1] |
| 19 |
|
| 20 |
Treat your computer's time like the time on your wrist watch, and set it |
| 21 |
maybe once a day. If it's out for any reason at all, move the hands to |
| 22 |
where they should be and be done with it. |
| 23 |
|
| 24 |
|
| 25 |
[1] virtual machines are a whole different topic. I'm assuming you don't |
| 26 |
have Gentoo in a guest VM. |
| 27 |
|
| 28 |
-- |
| 29 |
Alan McKinnon |
| 30 |
alan.mckinnon@×××××.com |
Archives