From owner-freebsd-current@FreeBSD.ORG Wed Jul 11 04:45:33 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A0BBF16A468 for ; Wed, 11 Jul 2007 04:45:33 +0000 (UTC) (envelope-from snezhko@indorsoft.ru) Received: from indorsoft.ru (indor.net.tomline.ru [213.183.100.90]) by mx1.freebsd.org (Postfix) with ESMTP id 0E18B13C44B for ; Wed, 11 Jul 2007 04:45:31 +0000 (UTC) (envelope-from snezhko@indorsoft.ru) Received: from SNEZHKO by indorsoft.ru (MDaemon.PRO.v7.2.2.R) with ESMTP id md50000219096.msg; Wed, 11 Jul 2007 11:45:24 +0700 From: Victor Snezhko To: Eric Anderson References: <46934301.5080302@fer.hr> <469379DE.2030605@freebsd.org> Date: Wed, 11 Jul 2007 11:45:21 +0700 In-Reply-To: <469379DE.2030605@freebsd.org> (Eric Anderson's message of "Tue, 10 Jul 2007 07:21:50 -0500") Message-ID: User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Processed: indor.net.tomline.ru, Wed, 11 Jul 2007 11:45:24 +0700 (not processed: spam filter disabled) X-Return-Path: snezhko@indorsoft.ru Cc: freebsd-current@freebsd.org, Ivan Voras Subject: Re: Debugging time X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jul 2007 04:45:33 -0000 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