From owner-freebsd-current  Wed Aug 19 12:31:14 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA14411
          for freebsd-current-outgoing; Wed, 19 Aug 1998 12:31:14 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14391
          for <freebsd-current@FreeBSD.ORG>; Wed, 19 Aug 1998 12:31:09 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id FAA23515;
	Thu, 20 Aug 1998 05:30:30 +1000
Date: Thu, 20 Aug 1998 05:30:30 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199808191930.FAA23515@godzilla.zeta.org.au>
To: freebsd-current@FreeBSD.ORG, jwd@unx.sas.com
Subject: Re: 13 months of user time?
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>   I found this on a 3 month old snap, and have now replicated it
>on 3.0-980818-SNAP.
>
>for i in /bin/*; do
>   time rsh nodename uptime
>done
>
>   Yields the following output:
>
>.....
> 2:00PM  up 1 day,  1:39, 1 user, load averages: 0.00, 0.00, 0.00
>   0.19s real    0.00s user    0.00s system 
> 2:00PM  up 1 day,  1:39, 1 user, load averages: 0.00, 0.00, 0.00
>   0.20s real 33554431.00s user    0.00s system 

This is probably just a symptom of a negative times bug and assorted
overflows.  This negative times bug usually kills processes with a
SIGXCPU.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message