[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
NTP Issues Today
On Tue, Nov 20, 2012 at 7:49 PM, Jimmy Hess <mysidia at gmail.com> wrote:
> Are you sure that you are actually using NTP to set your clock?
> For you to sync with 2000, you should have had multiple confused
> peers from multiple time sources; possibly a false radio signal....
> NTP by default has a panic threshold of 1000 seconds.
> This _should_ have caused NTP to execute a panic shutdown,
> instead of setting the clock back 30 million seconds.
For VMWare at least, their official recommendation for NTP is to
tinker panic 0
for suspend/resume reasons. I've seen it default in some places.