Bug 1825240

Summary: minor typos in documentation and man page nslcd.conf(5)
Product: Red Hat Enterprise Linux 7 Reporter: Filip Dvorak <fdvorak>
Component: nss-pam-ldapdAssignee: Tomas Halman <thalman>
Status: CLOSED WONTFIX QA Contact: Filip Dvorak <fdvorak>
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.8CC: fdvorak
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-17 07:27:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Filip Dvorak 2020-04-17 13:14:58 UTC
Description of problem:
When I was reading manual pages and documentation I have found some typos in nslcd.conf(5) and /usr/share/doc/nss-pam-ldapd-0.8.13/README

Version-Release number of selected component (if applicable):
rpm -qa | grep nss-pam-ldapd
nss-pam-ldapd-0.8.13-22.el7.1.x86_64


Steps to Reproduce:
Actual results:
1. grep srtongly /usr/share/doc/nss-pam-ldapd-0.8.13/README 
separately and are not srtongly tied together. This means that for instance

2.grep "This consist mostly" /usr/share/doc/nss-pam-ldapd-0.8.13/README 
module. This consist mostly of adding ldap in the list of lookup methods in

3.grep "that for when" /usr/share/doc/nss-pam-ldapd-0.8.13/README 
Note that for when using IPv6 hosts entries, the addresses in the LDAP

4.man nslcd.conf | grep substitb
              (use default) will substitbute the value of the attribute or, if               (use alternative) will substitbute word if attribute is set,

5.man nslcd.conf | grep sensetive
              match should be case-insensetive.  The default value is /^[a-z0-9._@$][a-z0-9._@$ \\~-]*[a-z0-9._@$~-]$/

Expected results:
1. strongly
2. This consists
3. Note when using....
4. substitute 
5. insensitive

Comment 6 RHEL Program Management 2021-10-17 07:27:06 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.