Bug 536840

Summary: initscript collected problems LSB-compilant ktune
Product: Red Hat Enterprise Linux 6 Reporter: Jan Ščotka <jscotka>
Component: tunedAssignee: Phil Knirsch <pknirsch>
Status: CLOSED CURRENTRELEASE QA Contact: Yulia Kopkova <ykopkova>
Severity: medium Docs Contact:
Priority: high    
Version: 6.0CC: dkovalsk, jvcelak, rvokal, twoerner, ykopkova
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: tuned-0.2.8-2.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-11 15:00:49 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:
Bug Depends On:    
Bug Blocks: 633349    

Comment 2 RHEL Program Management 2009-11-11 15:35:54 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 3 Thomas Woerner 2010-01-15 12:50:51 UTC
The only thing that can be fixed is the check for EUID=0. 

There is no daemon running, therefore there is no pid file. The lock file /var/lock/subsys/ktune is used to determine if the service is running.

Comment 9 RHEL Program Management 2010-03-17 16:56:14 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 10 Thomas Woerner 2010-05-04 09:54:23 UTC
Fixed in version tuned-0.2.8-2.el6.

Comment 14 releng-rhel@redhat.com 2010-11-11 15:00:49 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.