Date: Wed, 10 Oct 2018 13:10:38 +0200 (CEST) From: Wojciech Puchar <wojtek@puchar.net> To: Ian Lepore <ian@freebsd.org> Cc: Wojciech Puchar <wojtek@puchar.net>, Peter Jeremy <peter@rulingia.com>, freebsd-hackers@freebsd.org Subject: Re: ntpd strange problem Message-ID: <alpine.BSF.2.20.1810101309190.35592@puchar.net> In-Reply-To: <1539093981.72469.30.camel@freebsd.org> References: <alpine.BSF.2.20.1810041557330.94038@puchar.net> <20181005061829.GG21091@server.rulingia.com> <alpine.BSF.2.20.1810051122310.9032@puchar.net> <a31ca466-3ef6-8a66-10cc-1c24cd6dc928@FreeBSD.org> <alpine.BSF.2.20.1810062041490.7470@puchar.net> <1538855151.14264.54.camel@freebsd.org> <alpine.BSF.2.20.1810081315510.26846@puchar.net> <20181009052924.GJ21091@server.rulingia.com> <alpine.BSF.2.20.1810090841430.41943@puchar.net> <1539093981.72469.30.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>>> useful. >> this server is quite (actually excellently) stable and i trust it. > > When I asked for various outputs, I meant "when the unsync problem is > happening"; those outputs are uninteresting when everything is working > right. so i will look back and tell you WHEN it will happen again. > > You should remove the config for the "local" clock from your ntp.conf. > Configuring a bogus local clock is NEVER the right thing to do, and > it's even worse to configure it at a high stratum number. thank you. this is an error.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1810101309190.35592>