From owner-freebsd-bugs  Wed Oct 30 07:40:06 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA13794
          for bugs-outgoing; Wed, 30 Oct 1996 07:40:06 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA13759;
          Wed, 30 Oct 1996 07:40:02 -0800 (PST)
Date: Wed, 30 Oct 1996 07:40:02 -0800 (PST)
Message-Id: <199610301540.HAA13759@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: Bruce Evans <bde@zeta.org.au>
Subject: Re: bin/1927: User CPU time getting accounting as system time
Reply-To: Bruce Evans <bde@zeta.org.au>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR bin/1927; it has been noted by GNATS.

From: Bruce Evans <bde@zeta.org.au>
To: FreeBSD-gnats-submit@FreeBSD.ORG, markd@Grizzly.COM
Cc:  Subject: Re: bin/1927: User CPU time getting accounting as system time
Date: Thu, 31 Oct 1996 02:24:24 +1100

 >I ran an CPU intensive job, timing it with /usr/bin/time and the result was
 >     2097.84 real         0.00 user      2013.06 sys
 
 The statistics clock has apparently stopped.  This used to cause 0.00 for
 both the user and systm times, but I changed it so that times for short-
 lived processes are counted somewhere, and this has the side effect of
 counting all process times as system times if the statclock stops.
 
 Bruce