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.
First Last Prev Next    This bug is not in your last search results.
Bug 88874 - Wrong priority for artsd in top
Wrong priority for artsd in top
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: procps (Show other bugs)
9
athlon Linux
medium Severity low
: ---
: ---
Assigned To: Daniel Walsh
Brian Brock
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2003-04-15 04:09 EDT by Alexander Popov
Modified: 2007-04-18 12:53 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-02-05 11:35:40 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.)

  None (edit)
Description Alexander Popov 2003-04-15 04:09:43 EDT 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
The PRI section in top shows wrong priority for artsd: 18446744073709551565. I'm not sure if the problem is in the kernel, artsd or psutils. These are the versions of these packages on my system:
arts-1.1-7
kernel-2.4.20-9
psutils-1.17-19


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

How reproducible:
Always

Steps to Reproduce:
1. Simply run top and see the PRI column for artsd
2.
3.
    

Additional info:
Comment 1 Michael Lee Yohe 2003-04-15 10:40:54 EDT 
The package which contains the "top" command is procps.

$ rpm -qf `which top`
procps-2.0.11-6

"psutils" is a package that contains utilities for PostScript documents.

Have you restarted the daemon and noticed the behavior is consistent (the value
is the same no matter what)?  Did you upgrade to 9 or did you do a fresh install?
Comment 2 Alexander Popov 2003-04-15 11:30:51 EDT 
Sorry about psutils - my mistake ("dummy mode on" I guess)...

procps is 2.0.11-6 but I doubt the problem is in it...
I killed the daemon and started it manually - the priority was OK: 15
The situation repeats when I start X via "startx" though.
I made a clear install of 9 (didn't upgrade)...

Regards,
Sasho
Comment 3 Ngo Than 2003-10-23 06:03:28 EDT 
it looks like a bug in procps and probably was fixed in 2.0.11-7 or newer.
Comment 4 Alexander Larsson 2003-10-24 05:04:03 EDT 
Yes, this is the negative prio thing. It should be fixed in rawhide.
Comment 5 Alexander Popov 2003-10-24 06:24:51 EDT 
Thank you guys...
Should I change the status of this bug to resolve ( RAWHIDE )?
Comment 6 Alexander Larsson 2003-10-24 06:49:02 EDT 
if you've verified it fixed, yes.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.