On Jan 22, 2018, at 12:07 PM, Alan Somers <asom...@freebsd.org> wrote: > > * Sometimes the jumps happen immediately after ntpd adds a new server to > its list, but not always. > > * I'm using the default ntp.conf file. > > * ntpd is running on both, and it should be the only process touching the > clock. I have a script running "ntpq -c peers" once a minute, which shows > the offset for one server suddenly jump to a large negative number. Then > the offsets for other servers jump to the same value, then either ntpd > fixes the clock or exits because the offset is too high.
- Lose ntpd running in jails and run it only on the host. Running in the jail is totally unnecessary. - Is this a bare metal server or VM? Lots of clock issues with VM’s… - Stagger your periodic jobs on the host and the jail so they don’t all run at the same time slamming the host. -- inoc.net!rblayzor XMPP: rblayzor.AT.inoc.net PGP: https://inoc.net/~rblayzor/ _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
