Below procedure can be used to add a new NIS user when the passwd file is not in the /etc directory

Steps to Follow

The example below demonstrates how to add a user for NIS maps when the passwd file is not in the /etc directory.

The NIS directory is /etc/nisdir, where all the NIS maps reside.

Create a user in the /etc/passwd file. In this example, the new user is Johnl

Step 1.

Edit /etc/passwd to Add entry for the user

# vi /etc/passwd

Johnl:x:107:14:John l:/export/home/johnl:/bin/csh

Assign a password to the new user.

passwd johnl

Step 2:

Now run below command to create an entry in the shadow file

# pwconv

cat /etc/shadow file to see this entry in there.

johnl:dhXRywfkSELcE:10091::::::

Step 3:

Just copy the new entries to the /etc/nisdir/passwd file for passwd entry, and /etc/nisdir/shadow for shadow entry. To update the passwd map and push it to the slaves.

# make passwd

**NOTE**If you do not want this new user to be a local user, delete the entries in /etc/passwd and /etc/shadow.

Below procedure gives the steps to configure NIS Master Server, Slave Server and Client services in both solaris 9 and Solaris 10

Configuring NIS Master Server

You must login as root.

1.  Define the NIS domainname.

# domainname example-domain –> “example-domain” is the domain name.  It could be any name you like.

2.  Populate the /etc/defaultdomain file with the domainname.

# domainname > /etc/defaultdomain

3.  Edit the /etc/hosts file to ensure that the NIS master and all NIS slave servers have been defined and that a fully qualified name exists for this server.

4.  Optionally, create an alternate directory and copy the source files there.

#  mkdir  /var/yp/src

# cd /etc

# cp auto_home auto_master bootparams  ethers group hosts  netgroup netmasks networks passwd  protocols  publickey rpc services shadow timezone  user_attr  /var/yp/src Full Story

Changing an NIS slave server to a client is a three-part process:

1. Edit the ypservers map on your NIS master, removing the defunct slave from the list of servers.

2. on the NIS slave, remove NIS configuration

3. Convert the NIS slave as NIS client

**Note: Step 3 is optional and should be used only if we want turn the NIS slave into NIS client.

Step 1:

Removing NIS Slave from NIS Master’s ypservers map. When you initialize your NIS master, you give it a list of NIS slaves. If you later add additional NIS slaves, or remove one of these original NIS slaves, you must update the NIS list of servers. This is done entirely from the NIS master server. First, you must output the list of NIS servers:

nis_master# cd /var/yp/`domainname`

nis_master# makedbm -u ypservers > /tmp/ypservers

nis_master# vi /tmp/ypservers    and remove  slave from the list.

nis_master# makedbm /tmp/ypservers ypservers

verify removal via:

nis_master# ypcat -k ypservers

The slave server should no longer show up on this list. It is not necessary to reboot the master.  This change will take effect without stopping or restarting any processes.

Full Story

To add a slave server to an existing NIS domain do the following:

1. become root on master

2. cd /var/yp/`domainname`

3. /usr/etc/yp/makedbm -u ypservers > /tmp/tempfile

4. vi /tmp/tempfile
Add the new slave servers name on a new line twice in a row on the same line, i.e., slave1 slave1.

5. /usr/etc/yp/makedbm /tmp/tempfile  ypservers

6. Go to slave and run ypinit -s.

By following below steps we can NIS from client, Slave Server and Master Servers

  Full Story

There’s no local files implementation of netgroups.   Netgroups are used to group machines or users together in order to make certain sysadmin tasks easier.

A standard netgroup triple reads as follows: (hostname, username, domainname) Full Story