Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 159428

Summary: [PATCH] sysreport should not collect device nodes
Product: Red Hat Enterprise Linux 3 Reporter: David Lehman <dlehman>
Component: sysreportAssignee: Ngo Than <than>
Status: CLOSED DEFERRED QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: shillman
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-10-04 14:20:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
don't include any block or char device nodes in the sysreport none

Description David Lehman 2005-06-02 17:01:51 UTC
Description of problem:
sysreport collects device nodes if present from $DNSDIR/dev and
/proc/scsi/qla2300 as a consequence of collecting the /proc/scsi and $DNSDIR/
recursively. This is a problem because it means you need to be root to unpack
the sysreport.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Run sysreport on a system with qla2300 or a bind chroot set up
2. Try to unpack the sysreport as an unprivileged user 
Actual results:
tar fails trying to create device nodes

Expected results:
sysreports should be collected such that they can be unpacked by non-root users

Additional info:

Comment 1 David Lehman 2005-06-02 17:01:51 UTC
Created attachment 115097 [details]
don't include any block or char device nodes in the sysreport

Comment 3 Ngo Than 2005-10-04 14:20:32 UTC
This feature is now included in sysreport-1.4.2-3 from, which will be added in 
next comming RHEL5 release. 
In my opinion it's not worth to add it in RHEL3 update.