Bug 127306
Summary: | authconfig breaks NIS config when using multiple domains | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Uwe Menges <uwe.menges> |
Component: | authconfig | Assignee: | Tomas Mraz <tmraz> |
Status: | CLOSED DEFERRED | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | nphilipp |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-01 17:49:31 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 170445 |
Description
Uwe Menges
2004-07-06 13:00:21 UTC
Dear Uwe, 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. greetings, Jindrich 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. |