Date: Wed, 11 Jul 2007 11:45:21 +0700 From: Victor Snezhko <snezhko@indorsoft.ru> To: Eric Anderson <anderson@freebsd.org> Cc: freebsd-current@freebsd.org, Ivan Voras <ivoras@fer.hr> Subject: Re: Debugging time Message-ID: <uvecrczvi.fsf@indorsoft.ru> In-Reply-To: <469379DE.2030605@freebsd.org> (Eric Anderson's message of "Tue, 10 Jul 2007 07:21:50 -0500") References: <f6u94s$v6o$1@sea.gmane.org> <usl7wvnc9.fsf@indorsoft.ru> <46934301.5080302@fer.hr> <usl7w648w.fsf@indorsoft.ru> <469379DE.2030605@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Eric, >>>> For about half a year I have another weirdness with time on my >>>> -current box without vmware, maybe it's somehow has common origins >>>> ... >> When I just reboot FreeBSD, offset doesn't exceed one or two seconds >> (notably, bios takes longer to boot, about 5-10 seconds). When BSD is >> inactive for several hours, number is much bigger. >> >> I neglected to debug this deeply before - I assumed I have overlooked >> something simple, but now that you have reported another issue in the >> similar area, I'll try to collect full information. > > When you say 'inactive', do you mean that you have suspended the > machine in vmware, or it is 'powered off'? My machine isn't on vmware, it's a hardware box. I just power it off. Nevertheless, yesterday all the evening I hadn't internet access - thunderstorm has broken my wires. And guess what - ntpdate couldn't find ntp servers, but the system date was correct anyway. So I guess my issue has something to do with ntpdate. I didn't set any unusual flags, just ntpdate_enable="YES" and ntpdate_hosts="ntp.example.com". As the second invocation of ntpdate (by hand) always reported much offset which is less than a second, I think ntp servers (I tried two or three) is OK too. -- WBR, Victor V. Snezhko E-mail: snezhko@indorsoft.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?uvecrczvi.fsf>