Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 461616

Summary: Typos in kdump inistscript
Product: Red Hat Enterprise Linux 5 Reporter: Jay Turner <jturner>
Component: kexec-toolsAssignee: Neil Horman <nhorman>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.3CC: qcai, riek, srevivo
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 1.102pre-37.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-09-23 12:17:12 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:
Attachments:
Description Flags
kexec-tools patch none

Description Jay Turner 2008-09-09 14:06:28 UTC
Created attachment 316188 [details]
kexec-tools patch

Description of problem:
There are a few typos in the kdump initscript which don't appear to impact the kdump functionality, but do spit out errors.

Version-Release number of selected component (if applicable):
1.102pre-35.el5

How reproducible:
Always

Steps to Reproduce:
1. Start the kdump service, thus forcing the creation of the initrd
2. Stop kdump and then start it again.  Since no changes have been made, kdump should start up cleaning, but instead will spit out errors.

Comment 1 Neil Horman 2008-09-10 18:15:15 UTC
fixed in bz -32.el5.  Thanks!

Comment 3 Jay Turner 2008-09-11 11:45:41 UTC
Fix confirmed with kexec-tools-1.102pre-37.el5.  Will close out once that package is available in a compose.

** Note, comment 1 appears to have been a fat-finger.  The fix originally landed in -37.el5 just in case someone comes back looking for data later.

Comment 4 Jay Turner 2008-09-23 12:17:12 UTC
1.102pre-40.el5 included in beta-candidate trees (20080919.1 for Server and 20080919.2 for Client)