| 1 |
On Saturday 26 July 2014 12:31:55 Holger Hoffstätte wrote: |
| 2 |
> On Sat, 26 Jul 2014 15:05:23 +0300, Alexander Kapshuk wrote: |
| 3 |
> > Which NTPd package would the list recommend using, ntp, openntpd, or |
| 4 |
> > some other package? |
| 5 |
> |
| 6 |
> chrony - no competition, even for servers. ntpd is way overrated, |
| 7 |
> unnecessarily hard to setup correctly, fragile and contrary to |
| 8 |
> popular belief not even that accurate, unless you use external |
| 9 |
> HW clocks. Chrony is maintained by Red Hat in cooperation with the |
| 10 |
> timekeeping code in the kernel. |
| 11 |
|
| 12 |
I too have been using chrony since before I can remember, when ntpd could only |
| 13 |
step the clock. Chrony just works - I haven't even bothered to look round for |
| 14 |
an alternative. As the docs say (somewhere or other), if you run any kind of |
| 15 |
mail service, you certainly don't want your clock to step backwards suddenly. |
| 16 |
|
| 17 |
I didn't know Red Hat had taken over its maintenance - thanks for the info. |
| 18 |
|
| 19 |
-- |
| 20 |
Regards |
| 21 |
Peter |
Archives