| Re: [chrony-dev] chronyd not recovering after time stepped. |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
Hopefully spikes do not occur frequently (there would be more fundamental problems if they are frequent) and I think 60 secs is not a long time to wait for the current cycle to complete at which time the new drift would be applied.
The machine itself should not spike, unless some sysadmin decides to test it
by inserting spikes, and that also should not happen. If it does happen on its
own, either some program has gone rogue, and needs to be found and shot, or
there is something seriously wrong with the machine, and no amount of chrony
or ntp is going to solve it.
Similarly if the server suddenly spikes, that indicates something seriously
wrong there. That can be mitigated by using more than one independent server
sop the bad one gets outvoted (or removed as a server).
Ie, this situation does not seem to be one that can be fixed by tweaking
chrony. Rather it needs to be solved at source and spending huge time, effort,
and potentially introducing bugs on chrony does not seem a good way of
handling things.
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.