From owner-freebsd-current  Wed Aug 19 11:15:14 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA27909
          for freebsd-current-outgoing; Wed, 19 Aug 1998 11:15:14 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from lamb.sas.com (lamb.sas.com [192.35.83.8])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27903
          for <freebsd-current@freebsd.org>; Wed, 19 Aug 1998 11:15:11 -0700 (PDT)
          (envelope-from jwd@unx.sas.com)
Received: from mozart (mozart.unx.sas.com [192.58.184.8])
	by lamb.sas.com (8.8.7/8.8.7) with SMTP id OAA22047
	for <freebsd-current@freebsd.org>; Wed, 19 Aug 1998 14:14:28 -0400 (EDT)
Received: by mozart (5.65c/SAS/Domains/5-6-90)
	id AA28841; Wed, 19 Aug 1998 14:14:28 -0400
From: "John W. DeBoskey" <jwd@unx.sas.com>
Message-Id: <199808191814.AA28841@mozart>
Subject: 13 months of user time?
To: freebsd-current@FreeBSD.ORG
Date: Wed, 19 Aug 1998 14:14:27 -0400 (EDT)
X-Mailer: ELM [version 2.4 PL23]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi folks,

   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 
 2:00PM  up 1 day,  1:39, 1 user, load averages: 0.00, 0.00, 0.00
   0.20s real    0.02s user    0.00s system 
 2:00PM  up 1 day,  1:39, 1 user, load averages: 0.00, 0.00, 0.00
   0.19s real    0.00s user    0.01s system 
.....

   The values are very consistent until that 13 month value of
33554431.00s user time sneaks in. fyi: The value 33554431
repeats in all occurances of this bug...

   It seems to be coming from /usr/src/usr.bin/time/time.c:

        while (wait3(&status, 0, &ru) != pid);          /* XXX use waitpid */

   It would appear that there is a critter in our resource accounting?

   Has anyone else seen this problem?


   Comments? Critiques? Stupid user that can't count?  :-)

thanks,
John

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