NIS problem

[Brian D. McGrew]

In your /etc/sysconfig/network:

NETWORKING=yes
HOSTNAME=servername
NISDOMAIN=domainname  (NOT servername.domainame)

The ypserv script sets the domain name.

Make sure that the IP address of <servername> is defined in /etc/hosts
on the client machines or that they're on the same subnet as the server
and set to 'find' a server.

-brian
 
Brian D. McGrew        { brian at doubledimension.com ||
brian at visionpro.com }
--
> YOU!  Off my planet!
-----Original Message-----
From: redhat-list-bounces at redhat.com
[mailto:redhat-list-bounces at redhat.com] On Behalf Of Bjorn Andersen
Sent: Sunday, April 10, 2005 11:04 AM
To: General Red Hat Linux discussion list
Subject: NIS problem

Hi

I have a strange problem in my RHEL4 ES server.

The server is setup as a NIS and NFS server, and all the clients (RHEL4
WS clients) mount their /home's on the server (and another shared
folder /media/export).

The server runs fine, but recently i had to restart the server and found
out that NIS did not start with the server (or started before the NIS
domain was set). I have written in /etc/sysconfig/network:

NETWORKING=yes
HOSTNAME=Servername
NISDOMAIN=Servername.domainname



I have configured ypbind, yppasswdd, ypserv and ypxfrd to start when the
server boots. I used Webmin.


How can i be sure that the NIS domain name is set BEFORE the NIS servers
starts?



Regards
Bjorn Andersen

-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list