Bug 74704

Summary: Kernel re-prioritizing X (ioperm?)..
Product: [Retired] Red Hat Linux Reporter: Ali-Reza Anghaie <ali>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED CURRENTRELEASE QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: low    
Version: 8.0CC: mitr
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: 2003-06-05 19:25:30 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 Ali-Reza Anghaie 2002-10-01 01:04:30 UTC 
Description of Problem:   
   
The default kernel automagically nices X to -10. Why is the kernel futzing   
with userland process priorities? 
 
Version-Release number of selected component (if applicable):   
   
kernel-2.4.18-14   
XFree86-4.2.0-72   
   
How Reproducible:   
 
Always.  
 
Steps to Reproduce:   
1. Start X. Or boot into runlevel 5.  
2. ps -efl |grep X  or  top  
3. Cock head sideways at the X process priority. 
   
Actual Results:   
  
X is niced -10.  
   
Expected Results:   
   
X should be regular priority unless launched otherwise.  
  
Additional Information:   
  
I think it's much more sane to prioritize X by start-up scripts instead of  
handling it via the kernel. I really don't think the kernel should molest  
userland priorities as such. 
 
Setting to low/high as I think it's a low priority but it's a severe mistake 
IMO. 
 
Cheers, -Ali