Date: Tue, 10 Jul 2007 10:27:45 +0200 From: Ivan Voras <ivoras@fer.hr> To: Victor Snezhko <snezhko@indorsoft.ru> Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Debugging time Message-ID: <46934301.5080302@fer.hr> In-Reply-To: <usl7wvnc9.fsf@indorsoft.ru> References: <f6u94s$v6o$1@sea.gmane.org> <usl7wvnc9.fsf@indorsoft.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Victor Snezhko wrote: > Hi, Ivan, David, Hi, > For about half a year I have another weirdness with time on my > -current box without vmware, maybe it's somehow has common origins > with your behaviour. When I boot FreeBSD, ntpdate (which is set up to > run via rc.conf) often reports huge time offsets: > 10 Jul 12:04:34 ntpdate[51761]: step time server ntp.server.name offset 234456.074166 sec > > I have so far only noticed that the value of the the offset is roughly > equal to the amount of time when FreeBSD isn't running (this is a > dual-boot box with windows). The box is pretty old, 600-MHz Celeron Is the above number correct (i.e. ~~ 65 hours)? I noticed there can be a consistent "shift" of duration equal to your timezone when VMWare sets the RTC to the host's local time and FreeBSD thinks it's UTC. But if the difference is not constant, it's not it. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGk0MIldnAQVacBcgRAhjgAJ9mNV0Nyjy/iyD+88Y0W5gKUMMC3wCfeWkU 2xWQ2TGgr2TiELuHHg2158s= =81ct -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46934301.5080302>