Bug 682124 - sosreport does not capture nslcd.conf file.
sosreport does not capture nslcd.conf file.
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sos (Show other bugs)
Unspecified Unspecified
medium Severity medium
: rc
: 6.1
Assigned To: Keith Robertson
David Kutálek
Depends On:
Blocks: 830599
  Show dependency treegraph
Reported: 2011-03-04 03:40 EST by Najmuddin Chirammal
Modified: 2016-07-03 21:33 EDT (History)
9 users (show)

See Also:
Fixed In Version: 2.2-9.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 830599 (view as bug list)
Last Closed: 2011-12-06 13:10:31 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Najmuddin Chirammal 2011-03-04 03:40:52 EST
Description of problem:

sosreport does not capture the ldap configuration file /etc/nslcd.conf

Version-Release number of selected component 


How reproducible:

Steps to Reproduce:
1. Run sosreport,  List the contents of the generated archive
Actual results:

no nslcd.conf file.

Expected results:

sosreport only captures ldap.conf file, since nss-pam-ldapd use nslcd.conf file it should be included in the archive.
Comment 3 RHEL Product and Program Management 2011-04-03 22:16:04 EDT
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 7 errata-xmlrpc 2011-12-06 13:10:31 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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