Bug 1305721 - autofs.conf: Fix 'nameing' typo
Summary: autofs.conf: Fix 'nameing' typo
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: autofs
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Ian Kent
QA Contact: xiaoli feng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-09 00:54 UTC by Thomas Leavitt
Modified: 2016-11-04 07:44 UTC (History)
2 users (show)

Fixed In Version: autofs-5.0.7-55.el7
Doc Type: Bug Fix
Doc Text:
Cause: Spelling mistake. Fix: correct spelling mistake.
Clone Of:
Environment:
Last Closed: 2016-11-04 07:44:02 UTC
Target Upstream Version:

Attachments (Terms of Use)
Patch - fix 'nameing' typo in autofs.conf (1.30 KB, patch)
2016-05-06 08:06 UTC, Ian Kent 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2508 0 normal SHIPPED_LIVE autofs bug fix and enhancement update 2016-11-03 14:13:33 UTC

Description Thomas Leavitt 2016-02-09 00:54:56 UTC 
Description of problem: In comments, on line 118, there is a typo: "# Other common LDAP nameing" ... should be "naming"
Comment 2 Ian Kent 2016-02-09 02:13:16 UTC 
(In reply to Thomas Leavitt from comment #0)
> Description of problem: In comments, on line 118, there is a typo: "# Other
> common LDAP nameing" ... should be "naming"

Indeed yes, will fix.
Comment 3 Ian Kent 2016-05-06 08:06:45 UTC 
Created attachment 1154508 [details]
Patch - fix 'nameing' typo in autofs.conf
Comment 7 errata-xmlrpc 2016-11-04 07:44:02 UTC 
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.

https://rhn.redhat.com/errata/RHBA-2016-2508.html
Note You need to log in before you can comment on or make changes to this bug.