Bug 6150 – Initial "CPU States" in top are misleading

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 6150 - Initial "CPU States" in top are misleading

Summary:	Initial "CPU States" in top are misleading

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	procps (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	i386 Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Michael K. Johnson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-10-20 13:17 EDT by James Manning
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-11-03 14:43:08 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description James Manning 1999-10-20 13:17:30 EDT

For a heavily pegged system (4 CPU's, 4 gzip -9's) the
the "CPU States" line of top right after running states:

CPU states:  0.8% user,  0.2% system,  0.0% nice,  0.0% idle

on my RH 6.0 system, the initial line was:

CPU states:  0.6% user,  0.2% system,  0.7% nice,  0.5% idle

regardless of how pegged or idle the machine was...

I'd rather the states say -.-% or something more reflective
of the "unknown" status... or just not display that line
until accurate numbers are available.  Could an initial
poll be done to fill in at least reasonable numbers?

Comment 1 Michael K. Johnson 1999-11-03 14:43:59 EST

The "initial poll" is what fills in those urealistic numbers in the
first place.  I don't think that removing them the first time through
makes sense, as plenty of top's other numbers are the same way -- the
first shot is a snapshot, but many of the numbers depend on top's
history.

Note You need to log in before you can comment on or make changes to this bug.