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.
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.
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 From nivedita.com 2007-11-28 13:46 EDT------- Upping severity to match priority set by development team.
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 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.