Bug 461616 - Typos in kdump inistscript
Summary: Typos in kdump inistscript
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kexec-tools
Version: 5.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Neil Horman
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-09 14:06 UTC by Jay Turner
Modified: 2015-01-08 00:16 UTC (History)
3 users (show)

Fixed In Version: 1.102pre-37.el5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-09-23 12:17:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
kexec-tools patch (548 bytes, patch)
2008-09-09 14:06 UTC, Jay Turner
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2009:0105 0 normal SHIPPED_LIVE kexec-tools bug fix and enhancement update 2009-01-20 16:04:36 UTC

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)


Note You need to log in before you can comment on or make changes to this bug.