Bug 61017

Summary: getrusage() produces incorrect results for threads
Product: [Retired] Red Hat Linux Reporter: Need Real Name <daytona>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED CURRENTRELEASE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-09-30 15:39:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Need Real Name 2002-03-12 03:50:55 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4) Gecko/20011128
Netscape6/6.2.1

Description of problem:
the system call "getrusage" does not include user nor system time used by
threads.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
Use "pthread_create" to execute a thread that does some calculations.
Use "pthread_join" to wait for it to complete.
Call "getrusage" for self and again for children, it does not report the
user or system time used by the thread.

Actual Results:  The "getrusage" call did not report the correct times for threads.
I have verified that the same code compiled and run under FreeBSD, Irix,
and Solaris does produce the expected results showing the times used by threads.

Expected Results:  The "getrusage" call should include time used by threads

Additional info:

Comment 1 Bugzilla owner 2004-09-30 15:39:26 UTC
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/