Bug 211678 - mkdumprd should abort when it finds bad kdump location
Summary: mkdumprd should abort when it finds bad kdump location
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kexec-tools
Version: 5.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Neil Horman
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-10-20 19:11 UTC by Akira Imamura
Modified: 2007-11-30 22:07 UTC (History)
3 users (show)

Fixed In Version: 5.0.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-02-13 17:17:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
This patch based on -104.el5 can fix the problem (1.40 KB, patch)
2006-10-20 19:14 UTC, Akira Imamura 		no flags Details | Diff
View All

Description Akira Imamura 2006-10-20 19:11:52 UTC 
Description of problem:
mkdumprd should abort when it finds bad kdump location.

Version-Release number of selected component (if applicable):
kexec-tools-1.101-104.el5

How reproducible:
Always

Steps to Reproduce:
1. Specify a name of SSH server that doesn't really exist, in kdump.conf.
2. Run "service kdump restart"
3.
  
Actual results:
kdump service shows "Bad kdump location" as a warning, but starts up.

Expected results:
kdump service shows "Bad kdump location" as a warning, and then fails to
start up.

Additional info:
Comment 1 Akira Imamura 2006-10-20 19:14:19 UTC 
Created attachment 139021 [details]
This patch based on -104.el5 can fix the problem
Comment 2 Neil Horman 2006-10-20 19:17:07 UTC 
I think its easier just to change the continue to an exit 1
Comment 3 Akira Imamura 2006-10-20 19:24:28 UTC 
Sure. The way you said is easier than the patch I worked on.

Thanks,
Akira
Comment 4 Neil Horman 2006-10-20 19:51:21 UTC 
fixed in -105.el5.  Thanks!
Comment 5 Jay Turner 2007-02-13 17:17:28 UTC 
kexec-tools-1.101-164.el5 included in 20070208.0.
Note You need to log in before you can comment on or make changes to this bug.