Red Hat Bugzilla – Bug 98300
new update breaks mail.aliases
Last modified: 2007-04-18 12:55:23 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
Description of problem:
the new makedbm creates maps with spaces on the ends of keys. the -a option to
makdebm tries to cope with the various formats that alias entries can have, but
chokes on the most common:
it creates a key of 'alias ' and data of 'real'. a workaround is to use:
but the latter doesn't work if real is a :include:file entry.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create mail.aliases from standard /etc/aliases
2. ypmatch ftp mail.aliases
3. ypmatch 'ftp ' mail.aliases
Actual Results: #2 fails, #3 works.
Expected Results: #2 should work and #3 should fail.
actually, makedbm seems to be broken in a number of ways. my netgroup map was broken after the upgrade as well. i have large groups done as:
with various kinds of whitespace after netgroup and on each continuation line. i finally had to go to:
to make things work.
ypserv-2.8-0.80E breaks mail.aliases on Redhat 8 and Redhat 9.
"alias" will actutally become "alias " (one space)
ypmatch -k alias mail.alias will fail
ypmatch -k "alias " mail.alias gives
works just fine
ypmatch -k alias mail.aliases give
I've encountered this problem with the Redhat 9 update ypserv-2.8-0.9E.
Rather than try to workaround it by coddling makedbm with aliases
files that are to its liking, I decided to back up to an earlier
version of ypserv's makedbm.
The makedbm in stock RedHat 9's ypserv suffers from the same problem.
But the makedbm from RedHat 8.0's ypserv-2.5-1 doesn't. I installed
that in place of the broken one in /usr/lib/yp. It doesn't exhibit
this busted behavior, and the files it produces appear to be
compatible with ypserv-2.8-0.9E.
BTW, it looks like bug 99479 could be another instance of this same bug.
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.