Bug 231820

Summary: [Propose] Netdump verbose option
Product: Red Hat Enterprise Linux 4 Reporter: kenji kikuchi <kenji.kikuti>
Component: netdumpAssignee: Neil Horman <nhorman>
Status: CLOSED DUPLICATE QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: 4.3   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-03-12 14:15:29 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
my idea for changes none

Description kenji kikuchi 2007-03-12 10:59:15 UTC
Description of problem:

I would like to propose verbose option for netdump server. Currently, to make
sure if netdump has successfully finished, server administrators need to check
 - /var/crash/xxx/vmcore
 - /var/crash/xxx/log
 
I think it's not a easy step for the most of them, and administrators who set up
nedtump or take vmcore files are not always engineers who examine the vmcore files. 

In addition, these days, most of servers have an ASR (Automatic System Recovery)
function. ASR itself has the ability to restart the crashed system. I also
think, it's making server administrators' netdump works more difficult.

Also, these days, most of servers have large memory capacity, and putting lots
of physical memory makes netdump memory transmission process longer. 

I think if netdump server could list how much memory page has been successfully
received so far, and write logs when it send restart command to the netdump
client, administrators can easily find how netdump is working without waiting
vmcore and log file creation.  


I think adding verbose option helps server administrators. I'm attaching a patch
file. This is against netdump-0.7.16. Please check the changes.



Version-Release number of selected component (if applicable):
RHEL4 update3, netdump-0.7.16

Comment 1 kenji kikuchi 2007-03-12 10:59:15 UTC
Created attachment 149814 [details]
my idea for changes

Comment 2 Neil Horman 2007-03-12 14:15:29 UTC

*** This bug has been marked as a duplicate of 231365 ***