Date: Sat, 6 Oct 2018 20:43:03 +0200 (CEST) From: Wojciech Puchar <wojtek@puchar.net> To: Matthew Seaman <matthew@FreeBSD.org> Cc: freebsd-hackers@freebsd.org Subject: Re: ntpd strange problem Message-ID: <alpine.BSF.2.20.1810062041490.7470@puchar.net> In-Reply-To: <a31ca466-3ef6-8a66-10cc-1c24cd6dc928@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>
next in thread | previous in thread | raw e-mail | index | archive | help
>> what should i look at to find a source of problem > > Is this a virtual machine or bare metal? VMs tend to have a lot more bare metal. > > driftfile /var/db/ntpd.drift > > then ntpd will record how fast or slow the clock tends to run so it can > immediately account for that across restarts, rather than having to work it > out de-novo everytime ntpd gets restarted. > # cat /var/db/ntpd.drift 35.586 what else can i do?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1810062041490.7470>