Bug 474405

Summary: condor-low-latency daemon init script should change to reflect new package name
Product: Red Hat Enterprise MRG Reporter: Jeff Needle <jneedle>
Component: gridAssignee: Robert Rati <rrati>
Status: CLOSED ERRATA QA Contact: Jeff Needle <jneedle>
Severity: medium Docs Contact:
Priority: low    
Version: 1.1CC: jsarenik, matt
Target Milestone: 1.1.1   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 1.0-8 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-04-21 16:19:27 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 Jeff Needle 2008-12-03 17:55:12 UTC
# service condor-low-latency start
Starting Low-Latency daemon:                               [  OK  ]

It would be more consistent if that said:

Starting condor-low-Latency daemon:                        [  OK  ]

Same for stopping.

Comment 1 Robert Rati 2009-01-12 16:32:13 UTC
Fixed.  Change will be in:

condor-low-latency-1.0-7

Comment 2 Jan Sarenik 2009-01-29 09:22:25 UTC
Please build the new version of the package so I can verify.
Thank you.

Comment 3 Robert Rati 2009-01-29 21:50:47 UTC
1.0-7 had a problem with the init script patch for EL4 so it didn't build on RHEL4.  1.0-8 has been built for both EL5 and EL4.

Comment 4 Jan Sarenik 2009-02-10 08:30:13 UTC
rhel4:~# /etc/init.d/condor-low-latency restart
Stopping condor-low-latency daemon:                        [FAILED]
Starting condor-low-latency daemon:                        [  OK  ]

I have tested it on both RHEL5.3 and RHEL4.7 on i386
and as the initscripts are multiarch, I do not consider
important trying it on x86_64 in hope this kind of
thinking is allowed for QE...

Comment 6 errata-xmlrpc 2009-04-21 16:19:27 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2009-0434.html