Question:
How are chronyd and ntpd fundamentally different?
Particularly interested in the moment with a smooth adjustment of time. It is believed that chronyd cannot do this. How safe is it to use in production, especially when combined with services that are quite sensitive to time travel (which can be triggered by abrupt clock changes)? For example, the MySQL server may not survive an abrupt change in time for a few seconds and crash. Which, of course, is unacceptable in the current project.
Answer:
Chronyd still knows how! Moreover, by default, this is the mode that is activated. During operation Chronyd always smoothly adjusts the time if the makestep directive is absent (or a zero limit is specified). However, you can set the number of time adjustments at which the daemon can jump in the clock.