Red Hat Bugzilla – Bug 99479
mixed white space entries not matched in NIS maps
Last modified: 2015-01-07 19:05:50 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
Description of problem:
After the errata upgrade on our NIS server some automount map entries were no
longer being matched. They showed up in `ypcat -k auto.home' but not in
`ypmatch user auto.home'.
All the entries that failed had a space followed by one or more tabs between the
two fields of the map. All other entries had either all spaces or all tabs.
Changing the failing entries to all spaces or all tabs fixed the problem.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a NIS map with two fields separated by white space
2. For some entries separate the fields with a space followed by one or more tabs
3. do 'ypmatch name map_name' for the mixed white space entries
Actual Results: ypmatch returns:
Can't match key _user_ in map _map_. Reason: No such key in map
Expected Results: ypmatch should have shown the entry since ypcat -k _map_
This worked fine prior to the errata upgrade.
This is not serious since it's easily worked aroubd but in an environment like
ours where NIS maps have been imported from other OSes and maintained by several
generations of admins it might not be easy to see what the problem is. It was
only after looking at the maps using vi in :list mode that I was able to see it.
Otherwise the misbehaving entries looked identical to the good ones.
This problem is not benign. Existing and obviously correct NIS maps unexpectedly
stopped working and it was very hard to trace the problem down to particular
combinations of spaces and tabs in /etc files. Most text editors do not visually
distinguish between spaces and tabs, and, even worse, arbitrary convert tabs
into spaces and spaces into tabs. K.O.
fixed in ypserv-2.8-0.9E
Red Hat Linux and Red Hat Powertools are currently no longer supported by Red
Hat, Inc. In an effort to clean up bugzilla, we are closing all bugs in MODIFIED
state for these products.
However, we do want to make sure that nothing important slips through the
cracks. If, in fact, these issues are not resolved in a current Fedora Core
Release (such as Fedora Core 5), please open a new issues stating so. Thanks.