Bug 89
Summary: | ypbind fails because domainname is unset | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | johnb |
Component: | ypbind | Assignee: | David Lawrence <dkl> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.2 | CC: | johnb |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1998-11-17 00:37:13 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: |
Description
johnb
1998-11-16 14:30:00 UTC
We use the NISDOMAIN env variable in /etc/sysconfig/network to set the NIS domain. If $NISDOMAIN is defined and not empty the /etc/rc.d/rc.sysvinit will set the domainname correctly. The installer only asks about the DNS domain name, not NIS domain name. OK. But my /etc/sysconfig/network does define NISDOMAIN: NISDOMAIN="mcom.com" I don't know how that got set if not by the install. How else can it be set? In any event, to ask whether NIS and autofs should be enabled in the install and then not set the NIS Domainname is a bug. NIS/autofs doesn't work after a reboot. That's bad don't you think? |