From owner-freebsd-questions Thu Jan 20 16:19:42 2000 Delivered-To: freebsd-questions@freebsd.org Received: from sabmail.rresearch.com (ip18.gte13.rb1.bel.nwlink.com [207.202.150.18]) by hub.freebsd.org (Postfix) with ESMTP id A33531517E for ; Thu, 20 Jan 2000 16:19:37 -0800 (PST) (envelope-from scott@sabunix.rresearch.com) Received: from sabmail.rresearch.com (localhost [127.0.0.1]) by sabmail.rresearch.com (8.9.3/8.9.3) with ESMTP id QAA31871 for ; Thu, 20 Jan 2000 16:19:26 -0800 (PST) (envelope-from scott@sabmail.rresearch.com) Message-Id: <200001210019.QAA31871@sabmail.rresearch.com> To: freebsd-questions@FreeBSD.ORG Subject: Re: Odd gettimeofday() return values References: <20000120223950.A24986@strontium.scientia.demon.co.uk> In-reply-to: <20000120223950.A24986@strontium.scientia.demon.co.uk> From: Scott Blachowicz Reply-To: Scott.Blachowicz@seaslug.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <31868.948413966.1@sabmail.rresearch.com> Date: Thu, 20 Jan 2000 16:19:26 -0800 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Smithurst wrote: > I'd guess they're related, the numbers are quite close (relatively at > least). All I can suggest really is upgrade to the latest -STABLE, > unless someone has a better idea. I recall talk of this calcru problem > being fixed (I used to see it a bit, too, though I never noticed the > gettimeofday problem). I'd guess that the two problems derive from the same basic problem, though. I haven't been keeping up with the lists lately - would that talk of that calcru problem being fixed have happened in time for the 3.4 release? Well...so far so good with that 'sysctl' command, so maybe I won't have to hack it in... > For a temporary hack (*only* if upgrading is too much trouble) I'd > probably set tv_usec to zero and leave tv_sec alone (probably writing > some log message so you can tell if that's a possible cause of something > else breaking). Alternatively, write a loop to try gettimeofday up to > (say) five times until you get a valid result. Both of these hacks seem > unspeakably ugly though, upgrading doesn't. :-) Yeah...but sticking a quick hack in is an easy, sub-hour task. Upgrading is likely to take a bit longer...it's on my list of things to do, but it was on my list for a long time last time (I went from 2.2.2 to 3.2). But I might try it to see if it gets me anywhere trying to talk to my old Exabyte EXB-8200 8mm tape drive - when I have it on the bus, the boot process just hangs (along with some strange messages that I don't remember right now)...another day, another battle... Thanx, Scott.Blachowicz@seaslug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message