Bug 3206 - NIS domain never set -> ypbind failure.
NIS domain never set -> ypbind failure.
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: ypbind (Show other bugs)
6.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-06-02 03:08 EDT by H. Peter Anvin
Modified: 2015-01-07 18:37 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-06-02 04:55:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description H. Peter Anvin 1999-06-02 03:08:30 EDT
This problem was detected on SPARC, but is probably a
generic problem.

It seems that RedHat 6.0 no longer sets the nisdomainname
anywhere; I have checked all the login scripts and there is
neither a mention of nisdomainname nor of NISDOMAIN (from
/etc/sysconfig/network) anywhere in the startup scripts.

This machine is a yp client, so it has yp-tools and ypbind
installed, but not ypserv.
Comment 1 Jeff Johnson 1999-06-02 04:55:59 EDT
Run authconfig as root. That will (amongst other things) put
a "NISDOMAIN=whatever" line in /etc/sysconfig/network.

------- Email Received From  "H. Peter Anvin" <hpa@transmeta.com> 06/02/99 05:07 -------

Note You need to log in before you can comment on or make changes to this bug.