Bug 186320 - sysreport doesn't capture all autofs configuration files
Summary: sysreport doesn't capture all autofs configuration files
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: sos   
(Show other bugs)
Version: 4.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Bryn M. Reeves
QA Contact: BaseOS QE - Apps
Keywords: FutureFeature
Depends On:
TreeView+ depends on / blocked
Reported: 2006-03-22 21:35 UTC by Jeremy West
Modified: 2012-06-20 13:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 13:21:55 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Jeremy West 2006-03-22 21:35:51 UTC
Description of problem:
The problem is really more of an enhancement.  The sysreport utility seems to
only be programmed to pull the /etc/auto.master /etc/auto.misc and /etc/auto.net
files for a users installation.  The problem with this is many users name their
autofs files different names such as /etc/auto.direct or /etc/auto.nfs
Could we please use a wild card when pulling anything named auto.* so that we
can get all of these configuration files put into the sysreport.

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

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:  

You should be able to change the script to something like this (as given to me
by another technician)

for x in `/bin/ls /etc/auto.*`; do
     STATUS="Collecting information about system services ($(/bin/basename $x))"
     catiffile "$x"

Additional info:

Comment 1 Jiri Pallich 2012-06-20 13:21:55 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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