Changes

Jump to: navigation, search

OPS335 NIS Lab

298 bytes removed, 16:36, 14 January 2013
Partial update to F17.
* An NIS server is used to synchronize system files between machines in an NIS domain.
* In this lab you will set up your Fedora PC as both an NFS and NIS server. You will then use your VM's to serve as your NFS and NIS clients.
{{Admon/important|Prerequisites|Before you begin make sure your Fedora 16 17 host and virtual machines are up to date (yum update).
Ensure both host and VM's have firewalls set up according to prior labs and all labs have been completed.
Ensure that your NFS server is running on the host and exporting the '/home' directory. }}
===PART A: Setting up your NIS Server===
*Install the NIS server and client onto your f16 f17 host PC
yum install ypserv ypbind
*Add the following line to the bottom of the file /etc/sysconfig/network
systemctl enable ypxfrd.service
*Backup the configuration file for NIS databases
cp /var/yp/Makefile /var/yp/Makefile.orgorig
*Modify the following two lines in /var/yp/Makefile from
MINUID=500
===PART B: Adding VM03 to your NIS domain===
*Ensure you are your VM03 is still mounting your home directory from the host machine using autofs. If not revisit last weeks lab.
*Install ypbind on your vm03.
*SSH to vm03 using two terminals, following your logs with one using
*Start the ypbind server with the command.
systemctl start ypbind.service
{{Admon/important|SELinux and ypbind|You may encounter that SELinux denies the ypbind service. To get this working set SELinux to allow the ypbind service by running this command:}}
grep ypbind /var/log/audit/audit.log | audit2allow -M mypol
*Then to make the changes active run:
semodule -i mypol.pp
 
*Looking at your logs ensure that ypbind is registered with rpcbind, if it is unable your firewall may need to be adjusted.
*Now when you run the following command:
932
edits

Navigation menu