Red Hat Bugzilla – Bug 127306
authconfig breaks NIS config when using multiple domains
Last modified: 2007-11-30 17:07:02 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040514
Description of problem:
# cat /etc/yp.conf
domain server server hsdns01
domain sapdomain2 server hs0yp1
Run authconfig; use NIS (or leave it as NIS). It says
which obviously is wrong. It then writes another wrong /etc/yp.conf:
# cat /etc/yp.conf
domain server server hs0yp1
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. see description.
Expected Results: Don't break handcrafted config files!
Handle multiple domains correctly, present choice of available domains.
the version of authconfig behaves correctly with only one NIS domain.
Furthermore the authconfig prefers getting the NIS domain name from
/etc/sysconfig/network than from /etc/yp.conf so the last domain in
the yp.conf was replaced by it. See your /etc/sysconfig/network, where
you have NISDOMAIN=server. The export of authconfig is really a bug
that I'll try to fix. The parser writes hostnames in reversed order in
respect to the original file and any other domain tags except the
first one are written as ypserver.
Fixed in Fedora core development, authconfig-5.0.2-1, it shouldn't break configs
with multiple domains anymore.
This problem will be resolved in a future major release of Red Hat Enterprise
Linux. Red Hat does not currently plan to provide a resolution for this in a Red
Hat Enterprise Linux update for currently deployed systems.
With the goal of minimizing risk of change for deployed systems, and in response
to customer and partner requirements, Red Hat takes a conservative approach when
evaluating changes for inclusion in maintenance updates for currently deployed
products. The primary objectives of update releases are to enable new hardware
platform support and to resolve critical defects.