Bug 248557

Summary:	rtcheck package uses /sbin/rtcheck instead of /usr/bin/rtcheck
Product:	Red Hat Enterprise MRG	Reporter:	IBM Bug Proxy <bugproxy>
Component:	realtime-kernel	Assignee:	Luis Claudio R. Goncalves <lgoncalv>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	low
Version:	1.0	CC:	acme
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	0.6.4-2.el5rt	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-07-26 14: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 IBM Bug Proxy 2007-07-17 14:06:50 UTC

LTC Owner is: nivedita.com
LTC Originator is: jstultz.com


The rtcheck-0.6.4-1.el5rt package puts the rtcheck binary in /sbin/ rather then
/usr/bin/. 

This is problematic as rtcheck needs to be in the standard user path, as regular
users will invoke it when running the JVM.

The rtcheck binary just needs to be moved to /usr/bin/ or some other location in
the standard user path.

Comment 1 Tim Chavez 2007-07-23 20:40:06 UTC

Where as I agree it should probably move into a standard user path, I believe
the JVM calls it explicitly from /usr/local/bin right?  I'm not 100% this is
true.  Something worth asking John Kacur.

Comment 2 IBM Bug Proxy 2007-07-30 21:10:35 UTC

changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|OPEN                        |ASSIGNED




------- Additional Comments From jstultz.com (prefers email at johnstul.com)  2007-07-30 17:08 EDT -------
Package has updated w/ /usr/bin/rtcheck. 

Tested JVM run to verify it works and it appears to work fine. Marking fixed and
accepted.

Comment 3 IBM Bug Proxy 2007-11-28 18:50:34 UTC

------- Comment From nivedita.com 2007-11-28 13:46 EDT-------
Upping severity to match priority set by development team.

Comment 4 Luis Claudio R. Goncalves 2007-11-28 19:17:00 UTC

Hi, I understood that the fix had been already tested and approved in
comment#2... anyway, this has been fixed some time ago:

[lclaudio@lab linux-2.6.21.x86_64]$ rpm -q rtcheck
rtcheck-0.6.4-2.el5rt.x86_64
[lclaudio@lab linux-2.6.21.x86_64]$ rpm -qi rtcheck | grep "Build Date"
Release     : 2.el5rt                       Build Date: Tue 24 Jul 2007 04:17:31
PM BRT

[lclaudio@lab linux-2.6.21.x86_64]$ rpm -ql rtcheck
/etc/rc.d/init.d/rtcheck
/usr/bin/rtcheck
/usr/share/doc/rtcheck-0.6.4
/usr/share/doc/rtcheck-0.6.4/README
[lclaudio@lab linux-2.6.21.x86_64]$

Comment 5 IBM Bug Proxy 2007-11-28 19:25:34 UTC

------- Comment From nivedita.com 2007-11-28 14:23 EDT-------
Er, yes, I should have marked that internal only. I was just closing up
and cleaning loose ends. We keep the bugs open in this project until
the release actually goes out :). It was in TESTED/ACCEPTED state. No
new info here, just a correction on what the severity should have been.