From owner-freebsd-hackers Mon Apr 14 13:20:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA11612 for hackers-outgoing; Mon, 14 Apr 1997 13:20:42 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA11605 for ; Mon, 14 Apr 1997 13:20:34 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA10308; Mon, 14 Apr 1997 16:20:02 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 14 Apr 1997 16:20 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id PAA22067 for ; Mon, 14 Apr 1997 15:54:51 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id QAA26402 for freebsd-hackers@freefall.cdrom.com; Mon, 14 Apr 1997 16:01:20 -0400 (EDT) Date: Mon, 14 Apr 1997 16:01:20 -0400 (EDT) From: Thomas David Rivers Message-Id: <199704142001.QAA26402@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: "calcru: negative time" messages with 2.2.1 Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I keep getting "calcru: negative time: -XXX usec" messages from my 2.2.1 box. If it were running for quite some time, I would expect these - but it occurs right after boot up... The values aren't that large (say, -564, -599) - so I'm betting it's the 'usec' field which has gone negative (or very large positive) somehow (although, I'm expanding the printf() to ensure that's the case.) Can anyone thing of a reason why microtime() would behave so strangely? - Dave Rivers -