Bienvenue sur le site admin-sys

Si probleme(s) avec NIS : (HPUX)

Jerome ROBERT — 2009-04-17T16:53:00Z

Si probleme(s) avec NIS :

If You Receive an NIS "Server Not
Responding" Message

Issue the /usr/sbin/ping(1M) command on
the NIS client to make sure the NIS server is up and is reachable on
the network. If the ping command fails, either the server is down, or
the network has a problem. If the server is down, reboot it, or wait
for it to come back up. For information on troubleshooting network
problems, see Installing and Administering LAN/9000 Software .

To boot your NIS client without waiting
for the server to come up, boot the client in single user mode, set
NIS_CLIENT=0 in the /etc/rc.config.d/namsvrs file, then boot your
client the rest of the way up.

Issue the domainname command (with no
arguments) on both the NIS server and the NIS client to check whether
their domain names are the same. If they are different, log in as
root to the NIS client and issue the following command to change its
domain name :

domainname domainname

Issue the ps -ef command on the NIS
server to check whether ypserv is running. If it is not, follow these
steps :

1.In the /etc/rc.config.d/namesvrs file
on the NIS server, make sure the following variables are set :

NIS_MASTER_SERVER=1

2.Issue the following command to start
up the NIS server :

/sbin/init.d/nis.server start

Make sure an NIS server exists on the
same subnet as the NIS client. The client broadcasts its bind
request, and it binds to the first server that responds to the
request. Broadcasts do not cross gateways or routers, so the server
must be on the same subnet as the client in order to receive the bind
request. If you cannot configure an NIS server on the same subnet as
your NIS clients, see To Bind an NIS Client to a Server on a
Different Subnet.

If a User Cannot Log In

If the user has recently changed
passwords, ask the user to try logging in with the old password. If
the user can log in using the old password, follow these steps :

1.Issue the ps -ef command on the NIS
master server to make sure the yppasswdd daemon is running. If it is
not, issue the

following command to start all the NIS
server processes :

/sbin/init.d/nis.server start

2.Check the cron scripts on the slave
servers to make sure transfers of the passwd map from the master
server are frequent enough. Once per hour is usually frequent enough,
but frequent map transfers may cause too much network traffic. You
might want to schedule map transfers for late at night, and advise
users to make their password changes just before they go home.

Issue the following command on the NIS
client to determine which master server supplies the passwd map to
the client :

/usr/bin/ypwhich -m passwd

If the server does not respond, see If
You Receive an NIS 'Server Not Responding' Message.

If the ypwhich command returns the name
of the NIS master server, log in as root to the master server and
make sure the user has an entry in its /etc/passwd file. Then, issue
the following commands on the master server to generate the NIS
passwd database from the /etc/passwd file and push it to the NIS
slave servers :

cd /var/yp

/usr/ccs/bin/make passwd

Issue the domainname command (with no
arguments) to make sure the client's default domain is the domain
served by the NIS master server. If it is not, log in as root to the
NIS client, and issue the following command to change its domain
name :

domainname domainname

Issue the following command to check
whether the NIS client has an entry in the passwd database on the NIS
server to which it is bound :

/usr/bin/ypmatch username passwd

If the client has no entry in the
passwd database, issue the following command on the NIS server to
which the client is bound :

/usr/sbin/ypxfr passwd

This command transfers the passwd
database from the NIS master server to the server where you issue the
command.

If the user's NIS client is bound to a
slave server, make sure the slave server is listed in the NIS master
server's ypservers database. Follow these steps :

1.Issue the following command on the
NIS client to determine which server the client is bound to :

/usr/bin/ypwhich

2.Log into the NIS master server, and
issue the following command :

cd /var/yp/domainname

3.Issue the following command on the
NIS master server to write the contents of the ypservers database to
a temporary file :

/usr/sbin/makedbm -u ypservers >
tempfile

4.If the NIS slave server is not listed
in tempfile, use a text editor to add it, and then issue the
following command to rebuild the ypservers database :

/usr/sbin/makedbm tempfile ypservers

If you are using NIS compat mode, make
sure the NIS escape entry in the /etc/passwd file on the client does
not have an asterisk in the password field. On HP systems, the NIS
escape entry in the /etc/passwd file should be

+: :-2:60001:: :

If You Receive an "Unknown Host"
Message

Issue the following command to trace a
lookup of the unknown host :

/usr/contrib/bin/nsquery hosts hostname

The trace will indicate which name
services (BIND, NIS, NIS+, or /etc/hosts) were queried and in what
order. If your host is not performing lookups the way you want, see
Configuring the Name Service Switch for instructions on configuring
the Name Service Switch.

Issue the following command on the NIS
client to determine which master server supplies the hosts map :

/usr/bin/ypwhich -m hosts

If the server does not respond, see If
You Receive an NIS 'Server Not Responding' Message.

If the ypwhich command returns the name
of the NIS master server, log in as root to the master server and
make sure the unknown host is listed in its /etc/hosts file. Then,
issue the following commands on the master server to generate the NIS
hosts database from the /etc/hosts file and push it to the NIS slave
servers :

cd /var/yp

/usr/ccs/bin/make hosts

Issue the domainname command (with no
arguments) to make sure the client's default domain is the domain
served by the NIS master server. If it is not, log in as root to the
NIS client and issue the following command to change its domain name :

domainname domainname

Issue the following command to check
whether the unknown host is listed in the hosts database on the NIS
server to which the client is

bound :

/usr/bin/ypmatch hostname hosts

If the host is not listed in the hosts
database, issue the following command on the NIS server to which the
client is bound :

/usr/sbin/ypxfr hosts

This command transfers the hosts
database from the NIS master server to the server where you issue the
command.

If the NIS client is bound to a slave
server, make sure the slave server is listed in the NIS master
server's ypservers database. Follow these steps :

1.Issue the following command on the
NIS client to determine which server the client is bound to :

/usr/bin/ypwhich

2.Log in as root to the NIS master
server and issue the following command to change to the directory
where the domain databases reside :

cd /var/yp/domainname

3.On the NIS master server, issue the
following command to write the contents of the ypservers database to
a temporary file :

/usr/sbin/makedbm -u ypservers >
tempfile

4.If the NIS slave server is not listed
in tempfile, use a text editor to add it, and then issue the
following command to rebuild the ypservers database :

/usr/sbin/makedbm tempfile ypservers

If an NIS Client Cannot Bind to a
Server

If NIS commands return any of the
following messages,

ypcat : can't bind to an NIS server for
domain domainname

ypmatch : can't match key.

reason : can't communicate with ypbind

ypwhich : clntudp_create error
RPC_PROG_NOT_REGISTERED

then ypbind is not running on the
client. Issue the following command to start all the NIS client
processes :

/sbin/init.d/nis.client start

If NIS Returns Incorrect Information

Issue the following command on the NIS
client to determine which master server supplies the appropriate NIS
map :

/usr/bin/ypwhich -m mapname

If the server does not respond, see If
You Receive an NIS 'Server Not Responding' Message.

Log in as root to the NIS master
server, and issue the following command to check the contents of the
appropriate NIS map :

/usr/bin/ypcat -k mapname

If the map contents are not correct,
edit the ASCII file from which the map is generated. Then issue the
following commands to regenerate the map and push it to the slave
servers :

cd /var/yp

/usr/ccs/bin/make mapname

domainname domainname

Issue the following command on the NIS
client to check the contents of the map on the NIS server to which
the client is bound :

/usr/bin/ypcat -k mapname

If the contents are not correct, log in
as root to the server that serves the NIS client, and issue the
following command :

/usr/sbin/ypxfr mapname

This command transfers the map from the
NIS master server to the server where you issue the command.

If the NIS client is bound to a slave
server, make sure the slave server is listed in the NIS master
server's ypservers database. Follow these steps :

1.Issue the following command on the
NIS client to determine which server the client is bound to :

/usr/bin/ypwhich

2.Log in as root to the NIS master
server and issue the following command to change to the directory
where the domain databases reside :

cd /var/yp/domainname

3.On the NIS master server, issue the
following command to write the contents of the ypservers database to
a temporary file :

/usr/sbin/makedbm -u ypservers >
tempfile

4.If the NIS slave server is not listed
in tempfile, use a text editor to add it, and then issue the
following command to rebuild the ypservers database :

/usr/sbin/makedbm tempfile ypservers

Make sure the slave servers have cron
scripts that schedule regular updates of the map.

Configuration d'un client NIS : (HPUX)

Jerome ROBERT — 2009-04-17T15:07:36Z

Configuration d'un client NIS :

en bref :

vérifier si ypserv tourne sur le
Master ?

personnalisé les fichiers
/etc/passwd et /etc/group

domainname domainname

modifier /etc/rc.config.d/namesvrs

/sbin/init.d/nis.client stop

/sbin/init.d/nis.client start

1° modification du fichier /etc/passwd :

Supprimer toutes les entrées superieure ou egale a 100 pour
UID

Ajouter la ligne ci dessous a la fin :

+: :-2:60001:: :

Le signe (+) signifie au processuse de
login d'aller voir les NIS.

The -2 in the user ID field restricts
the access of people who may attempt to log in using "+" as
a valid user name when NIS is not running. Anyone who successfully
logs in as "+" will be granted only the access permissions
of user nobody.

Pour plus d'information man 4 passwd

exemple :

root:0AnhFBmriKvHA:0:3: :/ :/bin/ksh

daemon :*:1:5: :/ :/bin/sh

bin :*:2:2: :/bin :/bin/sh

adm :*:4:4: :/usr/adm :/bin/sh

uucp :*:5:3: :/usr/spool/uucppublic :/usr/lib/uucp/uucico

lp :*:9:7: :/usr/spool/lp :/bin/sh

hpdb :*:27:1:ALLBASE :/ :/bin/sh

+: :-2:60001:: :

2° modification du fichier /etc/group :

Supprimer tous les groupes non
systemes

Supprimer toutes les entrées
superieure ou egale a 100 pour UID

Ajouter la ligne ci dessous a la fin :

+ :* :*

exemple :

root::0:rootl,sam

other::1 :

bin::2 :

sys::3 :

adm::4 :

daemon::5 :

mail::6 :

lp::7 :

+ :* :*

3° vérification

vérifier que le serveur NIS
fonctionne, et que ypserv est en mémore.

modification /etc/rc.config.d/namesvrs
avec :

NIS_DOMAIN=domainname

NIS_SLAVE_SERVER=0

NIS_CLIENT=1

NIS_MASTER_SERVER=0

4° rien ne va plus ...

/sbin/init.d/nis.client stop

/sbin/init.d/nis.client start

pour tester faite la commande suivant :

/usr/bin/ypwhich -m

pour en savoir plus ....

To Tell Users How to Use yppasswd

Tell all the users in your NIS domain
that they must use /usr/bin/yppasswd or passwd -r nis instead of the
passwd command when they want to change their login passwords.

Tell users that, when they want to
change their login passwords, they should do so just before they
leave for the day. This will allow time for the updated NIS maps on
the master server to be pushed to the slave servers.

The yppasswd command is a link to the
passwd -r nis command. It changes the /etc/passwd file on the NIS
master server, regenerates the NIS passwd maps from the updated
/etc/passwd file, and then pushes the NIS passwd maps to the slave
servers.

For more information, see the following
man pages : yppasswd(1), yppasswdd(1M), passwd(1), ypxfr(1M), and
yppush(1M).

To Prevent a Client from Binding
to Unknown Servers

1.On the NIS client, create a file
called /var/yp/secureservers, if it does not already exist.

2.Add lines to the file with the
following syntax :

address_mask IP_address

The IP_address is the internet address
of an NIS server or the subnet of an NIS server from which the client
will accept NIS information.

The address_mask indicates which bits
in the IP_address field are important. If a bit is set in the
address_mask field, the corresponding bit in the address of any NIS
server must match the same bit in the IP_address field.

3.Issue the following commands to kill
and restart the ypbind process :

/sbin/init.d/nis.client stop

/sbin/init.d/nis.client start

If an NIS server host has multiple
network interface cards, add a line to the secureservers file for the
IP address of each card.

If you start ypbind with the -ypset
option and issue the ypset command to bind to a specific server, the
/var/yp/secureservers file is ignored, and the client may bind to any
server.

Type man 1M ypbind at the HP-UX prompt
for more information.

Examples from /var/yp/secureservers

The following line from a
/var/yp/secureservers file allows the NIS client to bind only to the
server at IP address 20.21.22.23. Because every bit is set in the
address mask, the IP address of the NIS server must match the
IP_address field exactly, or the client will not bind to it.

255.255.255.255 20.21.22.23

The following line from a
/var/yp/secureservers file allows the client to bind to any NIS
server on the network 20.21.22.0. The last 8 bits of the server's IP
address are ignored, because the last 8 bits of the address mask are
set to 0. The client may bind to any server whose IP address begins
20.21.22.

255.255.255.0 20.21.22.23

To Bind an NIS Client to a Server on a
Different Subnet Hewlett-Packard recommends that you configure a
server on each subnet where you have NIS clients ; however, if you
cannot do that, follow these steps to force an NIS client to bind to
a server on a different subnet :

1.Log in as root to the NIS client.

2.Add the -ypset option to the
YPBIND_OPTIONS variable in the /etc/rc.config.d/namesvrs file, as
follows :

YPBIND_OPTIONS="-ypset"

3.In the /etc/rc.config.d/namesvrs
file, set the YPSET_ADDR variable to the IP address of an NIS server,
as in the following example :

YPSET_ADDR="15.13.115.168"

4.Issue the following commands to
restart the NIS client :

/sbin/init.d/nis.client stop

/sbin/init.d/nis.client start

If the server you specify in the ypset
command is unavailable when your client boots up, your client will
broadcast a request for a server to its local network. If no server
exists on the local network, the client will hang.

For more information, type man 1M ypset
or man 1M ypbind.

Configuration d'un serveur NIS escale (HPUX)

Jerome ROBERT — 2009-04-17T15:04:16Z

Configuration d'un serveur NIS escale :

en bref :

vérifier si ypserv tourne sur le
Master ?

personnalisé les fichiers
/etc/passwd et /etc/group

modificer le PATH de root :
PATH=$PATH :/var/yp :/usr/lib/netsvc/yp :/usr/ccs/bin

domainname domainname

/usr/etc/yp/ypinit -s serveur_nis_master

modifier /etc/rc.config.d/namesvrs

/sbin/init.d/nis.server start

/sbin/init.d/nis.client start

1° modification du fichier /etc/passwd :

Supprimer toutes les entrées superieure ou egale a 100 pour
UID

Ajouter la ligne ci dessous a la fin :

+: :-2:60001:: :

Le signe (+) signifie au processuse de
login d'aller voir les NIS.

Pour plus d'information man 4 passwd

exemple :

root:0AnhFBmriKvHA:0:3: :/ :/bin/ksh

daemon :*:1:5: :/ :/bin/sh

bin :*:2:2: :/bin :/bin/sh

adm :*:4:4: :/usr/adm :/bin/sh

uucp :*:5:3: :/usr/spool/uucppublic :/usr/lib/uucp/uucico

lp :*:9:7: :/usr/spool/lp :/bin/sh

hpdb :*:27:1:ALLBASE :/ :/bin/sh

+: :-2:60001:: :

2° modification du fichier /etc/group :

Supprimer tous les groupes non
systemes

Supprimer toutes les entrées
superieure ou egale a 100 pour UID

Ajouter la ligne ci dessous a la fin :

+ :* :*

exemple :

root::0:rootl,sam

other::1 :

bin::2 :

sys::3 :

adm::4 :

daemon::5 :

mail::6 :

lp::7 :

+ :* :*

3° vérification

vérifier que le serveur NIS
fonctionne, et que ypserv est en mémore.

modification du PATH de root :

PATH=$PATH :/var/yp :/usr/lib/netsvc/yp :/usr/ccs/bin

modification /etc/rc.config.d/namesvrs
avec :

NIS_DOMAIN=domainname

NIS_SLAVE_SERVER=1

NIS_CLIENT=1

NIS_MASTER_SERVER=0

4° rien ne va plus ...

/usr/bin/domainname domainname

domainname est le nom du domain NIS

/usr/sbin/ypinit -s NIS_server_name [DOM=domainname]

/sbin/init.d/nis.server start

/sbin/init.d/nis.client start

5° plannification des mises à jours :

cp /usr/newconfig/var/yp/ypxfr_1perday /var/yp

cp /usr/newconfig/var/yp/ypxfr_2perday /var/yp

cp /usr/newconfig/var/yp/ypxfr_1perhour /var/yp

crontab -l > fichier_crontab

# cela permet de concerver l'existant

Ajouter les trois lignes au fichier

"fichier_crontab"

0 21 * * * /var/yp/ypxfr_1perday

30 5,19 * * * /var/yp/ypxfr_2perday

15 * * * * /var/yp/ypxfr_1perhour

crontab fichier_crontab

Pour plus d'information ....

For more information, see the following
man pages : domainname(1), ypinit(1M), and ypfiles(4).

To Verify Your NIS Slave
Server Configuration

1.Log in as root to the slave server.

2.In the /etc/rc.config.d/namesvrs
file, add -ypset to the YPBIND_OPTIONS variable :

YPBIND_OPTIONS="-ypset"

3.Issue the following commands to
restart ypbind (the NIS client process) on the slave server :

/sbin/init.d/nis.client stop

/sbin/init.d/nis.client start

4.Issue the following command to force
the NIS client process on the slave server to bind to the server
process on the same host :

/usr/sbin/ypset slave_server_name

5.Issue the following command to check
whether the NIS slave server is working :

/usr/bin/ypwhich

The ypwhich command should return the
host name of the slave server.

If the ypwhich command does not return
the name of the slave server, il y a un probleme ....

6.In the /etc/rc.config.d/namesvrs
file, remove -ypset from the YPBIND_OPTIONS variable :

YPBIND_OPTIONS=""

7.Issue the following commands to
restart ypbind (the NIS client process) on the slave server :

/sbin/init.d/nis.client stop

/sbin/init.d/nis.client start

For more information, see the following
man pages : ypbind(1M), ypset(1M), and ypwhich(1).

To Schedule Regular Map
Transfers from the NIS Master Server

1.Log in as root to the slave server.

2.Copy the ypxfr_1perday,
ypxfr_2perday, and ypxfr_1perhour scripts from the
/usr/newconfig/var/yp directory to the /var/yp directory :

cp /usr/newconfig/var/yp/ypxfr_1perday
/var/yp

cp /usr/newconfig/var/yp/ypxfr_2perday
/var/yp

cp /usr/newconfig/var/yp/ypxfr_1perhour
/var/yp

3.Create a crontab file that invokes
these files at regular times. Following is an example crontab file :

0 21 * * * /var/yp/ypxfr_1perday

30 5,19 * * * /var/yp/ypxfr_2perday

15 * * * * /var/yp/ypxfr_1perhour

This file runs the ypxfr_1perday script
at 9:00 PM every night.

It runs the ypxfr_2perday script at
5:30 AM and 7:30 PM every day.

It runs the ypxfr_1perhour at 15
minutes past every hour.

4.Issue the following command to enter
the file into crontab,

crontab filename

where filename is the crontab file you
just created.

If you have created customized NIS maps
for your domain, you will have to add them to the appropriate
scripts.

You can also use the scripts provided
as templates for creating your own scripts.

In some domains, transferring the
passwd maps once per hour generates too much network traffic.

If you find this is the case, schedule
transfers of the passwd maps for less frequent intervals.

If you have multiple slave servers,
schedule map transfers for different times on different servers, so
all the servers are not performing transfers at the same time.

For more information, see the following
man pages : cron(1M), crontab(1), and ypxfr(1M).

To Restrict Access to the
Slave Server

1.On the NIS slave server, create a
file called /var/yp/securenets, if it does not already exist.

2.Add lines to the file with the
following syntax :

address_mask IP_address

The IP_address is the internet address
of an NIS client, NIS slave server, or subnet that may request NIS
information or transfer NIS maps from the NIS master server.

The address_mask indicates which bits
in the IP_address field are important.

If a bit is set in the address_mask
field, the corresponding bit in the source address of any incoming
NIS

requests must match the same bit in the
IP_address field.

3.Issue the following commands to kill
and restart the ypserv process :

/sbin/init.d/nis.server stop

/sbin/init.d/nis.server start

If a client or slave host has multiple
network interface cards, add a line to the securenets file for the IP
address of each card.

Type man 4 securenets at the HP-UX
prompt for more information.

Examples from /var/yp/securenets

The following line from a
/var/yp/securenets file allows only the NIS client at IP address
10.11.12.13 to request information from the NIS slave server. Because
every bit is set in the address mask, the source IP address on the
NIS request must match exactly, or the slave server will not return
the requested information.

255.255.255.255 10.11.12.13

The following line from a
/var/yp/securenets file allows any host on the network 10.11.12.0 to
request NIS information or transfer NIS maps from the slave server.
The last 8 bits of the IP address are ignored, because the last 8
bits of the address mask are set to 0. Any host whose IP address
begins 10.11.12 will be allowed access to the slave server.

255.255.255.0 10.11.12.13

Configuration d'un serveur NIS maître HPUX

Jerome ROBERT — 2009-04-17T15:02:37Z

Configuration d'un serveur NIS maître :

en bref :

concaténation de tout les
fichiers du parc pour un créer un de chaque sur le serveur
NIS.

pour le fichier passwd :

sur le serveur NIS, il doit y
avoir que les utilisateurs
sur les clients , il doit y avoir
root, et les démons

pour le fichier group :

sur le serveur NIS, il doit y
avoir que les groupes utilisateurs
sur les clients, il doit y avoir
que les groupes systemes

pour le fichiers hosts :

sur le serveur NIS, il ne doit pas
avoir de doublon IP, nom de machine et d'alias.
sur les clients, on pourra
supprimer ce fichier (cf. configuration d'un client NIS)

puis modifier /etc/rc.config.d/namesvrs
et /var/yp/Makefile

copier les fichiers a mapper dans
/var/yp/etc/ ( ou cp -r /etc /var/yp/etc/ , mais c'est pas bien
!!!)

modificer le PATH de root :
PATH=$PATH :/var/yp :/usr/lib/netsvc/yp :/usr/ccs/bin

/usr/bin/domainname domainname

/usr/sbin/ypinit -m

/sbin/init.d/nis.server start

/sbin/init.d/nis.client start

A. préparation des fichiers passwd, group, hosts.

1° récuperation de tout les fichiers /etc/passwd du parc de la société.

sur chaque machine cliente :

cp /etc/passwd /etc/passwd.$(hostname)

ATTENTION : dans le fichier
passwd des futur clients NIS, il doit y avoir que les demons et aucun
utilisateur.

puis copier
/etc/passwd.$(hostname) sur le serveur NIS dans /var/yp/etc/

sur le serveur NIS :

cp /etc/passwd /var/yp/etc/passwd

2° traitement du fichier passwd sur le serveur NIS :

ATTENTION : dans le fichier
passwd du serveur NIS, il doit y avoir que les utilisateurs et aucun
demon.

cd /var/yp/etc

cat passwd passwd.hostname1 passwd.hostname2... > passwd.temp

sort -o /var/yp/etc/passwd.temp -t : -k1,1 /var/yp/etc/passwd.temp

Cette derniere commande permet trier le
fichier pour faciliter la recherche des logins en double.

Il ne faut pas de doublon dans le
login.

sort -o /etc/passwd.temp -t : -k3n,3 /etc/passwd.temp

Cette derniere commande permet trier le
fichier pour faciliter la recherche des UID en double.

Il ne faut pas de doublon dans les UID.

Quand le fichier est correct :

mv /var/yp/etc/passwd.temp /var/yp/etc/passwd

rm /var/yp/etc/passwd.*

3° récuperation de tout les fichiers /etc/group du parc de la société

sur chaque machine cliente :

cp /etc/group /etc/group.$(hostname)

puis copier /etc/group.$(hostname) sur
le serveur NIS dans /var/yp/etc/

sur le serveur NIS :

cp /etc/group /var/yp/etc/group

4° traitement du fichier group sur le serveur NIS :

cd /var/yp/etc

cat group group.* > group.temp

sort -o /var/yp/etc/group.temp -t : -k1,1 /var/yp/etc/group.temp

Cette derniere commande permet trier le
fichier pour faciliter la recherche des noms de groupe en double.

Il ne faut pas de doublon dans les noms
de groupe.

sort -o /etc/group.temp -t : -k3n,3 /etc/group.temp

Cette derniere commande permet trier le
fichier pour faciliter la recherche des GID en double.

Il ne faut pas de doublon dans les GID.

Quand le fichier est correct :

mv /var/yp/etc/group.temp /var/yp/etc/group

rm /var/yp/etc/group.*

5° récuperation de tout les fichiers /etc/hosts du parc de la société

sur chaque machine cliente :

cp /etc/hosts /etc/hosts.$(hostname)

puis copier /etc/hosts.$(hostname) sur
le serveur NIS dans /var/yp/etc/

sur le serveur NIS :

cp /etc/hosts /var/yp/etc/hosts

6° traitement du fichier hosts sur le serveur NIS :

cd /var/yp/etc

cat hosts hosts.* > hosts.temp

sort -o /etc/hosts.temp /etc/hosts.temp

Cette derniere commande permet trier le
fichier pour faciliter la recherche des IP en double.

Il ne faut pas de doublon dans les
addresses IP.

sort -o /etc/hosts.temp -b -k2,2 /etc/hosts.temp

Cette derniere commande permet trier le
fichier pour faciliter la recherche des noms de machines en double.

Il ne faut pas de doublon. Ainsi que
dans les alias de machine.

Quand le fichier est correct :

mv /var/yp/etc/hosts.temp /var/yp/etc/hosts

rm /var/yp/etc/hosts.*

B. Modification des fichiers de configuration :

1° modification de /etc/rc.config.d/namesvrs :

# domainname represente le nom
du domaine NIS

NIS_DOMAIN=domainname

NIS_MASTER_SERVER=1

NIS_CLIENT=1

NIS_SLAVE_SERVER=0

YPPASSWDD_OPTIONS="/var/yp/etc/passwd -m passwd
PWFILE=/var/yp/etc/passwd"

2° modification de /var/yp/Makefile

Dans ce fichier, il va falloir modifier
la variable DIR :

DIR=/var/yp/etc/

Et modifier la liste de fichier a
mapper :

pour cela, /all : (c'est une cmd de
vi) , cela va nous positionner sur le paragraphe all, ce dernier
liste les fichier a mapper.

Il faud maintenant vérifier
l'existance de ces derniers dans /etc et les copier dans /var/yp/etc/

C. Création du serveur NIS

1° modification du PATH de root :

PATH=$PATH :/var/yp :/usr/lib/netsvc/yp :/usr/ccs/bin

2° Bientôt fin

# domainname represente le nom du
domaine NIS

/usr/bin/domainname domainname

/usr/sbin/ypinit -m

La commande ypinit permet de créer
un serveur nis, en lisant ses informations dans /var/yp/Makefile. Il
faudra lui indiquer les serveurs shaves s'il y en a. Pour sortir,
appuyer sur "Entree".

3° Joueur ou pas joueur ??

shutdown -r 0

/sbin/init.d/nis.server start

/sbin/init.d/nis.client start

4° La minute de vérité ...

/usr/bin/ypwhich -m #doit nous afficher la liste de table généré.

Pour en savoir plus ....

To Restrict Client and Slave Server Access to the
Master Server

On the NIS master server, create a file called /var/yp/securenets,
if it does not already exist.
Add lines to the file with the following syntax :
```
address_mask IP_address
```
The IP_address is the internet address of an NIS
client, NIS slave server, or subnet that may request NIS information
or transfer NIS maps from the NIS master server.

The address_mask indicates which bits in the
IP_address field are important. If a bit is set
in the address_mask field, the corresponding bit
in the source address of any incoming NIS requests must match the
same bit in the IP_address field.
Issue the following commands to
kill and restart the ypserv process :
```
/sbin/init.d/nis.server stop /sbin/init.d/nis.server start
```

If a client or slave host has multiple network interface cards,
add a line to the securenets file for the IP address of
each card.

Type man 4 securenets at the HP-UX prompt for more
information.

Examples from /var/yp/securenets

The
following line from a /var/yp/securenets file allows
only the NIS client at IP address 10.11.12.13 to request information
from the NIS master server. Because every bit is set in the address
mask, the source IP address on the NIS request must match exactly, or
the master server will not return the requested information.

255.255.255.255 10.11.12.13

The following line from a /var/yp/securenets file allows
any host on the network 10.11.12.0 to request NIS information or
transfer NIS maps from the master server. The last 8 bits of the IP
address are ignored, because the last 8 bits of the address mask are
set to 0. Any host whose IP address begins 10.11.12 will be allowed
access to the master server.

255.255.255.0 10.11.12.13

To Check the Contents of an NIS Map

Issue
the following command to verify that an NIS map contains the data
you expect it to contain :
```
/usr/bin/ypcat -k mapname
```

The -k option lists the key for each item in the map
as well as the data associated with the key. For example, in the
netgroup map, the netgroup name is the key. Without the

-k option, ypcat would list all the data
associated with each netgroup name, but not the netgroup name itself.

For more information on the ypcat command, type

man 1 ypcat

at the HP-UX prompt.

To Modify an NIS Map

Log in as root to the NIS
master server.
Make your changes to the source file for the NIS map. For
example, if you want to change the NIS hosts map, make
your changes to the /etc/hosts file.
Issue the following commands to generate the map and push it
to the slave servers :
```
cd /var/yp /usr/ccs/bin/make mapname
```
If your slave servers are not up and running yet,
run the make command with the NOPUSH flag
set to 1 :
```
cd /var/yp /usr/ccs/bin/make NOPUSH=1 mapname
```

This procedure works for all NIS maps
except the ypservers map, which has no source file. For
instructions on modifying the ypservers map,

If you make changes to the passwd,
group, or hosts maps, regenerate the

netid.byname map. The netid.byname map is a
mapping of users to groups, where each user is followed by a list of
all the groups to which the user belongs. The netid.byname
map is generated from the /etc/passwd and /etc/group
files.

For more information, see the following man pages : make(1),

ypmake(1M), yppush(1M), and ypxfr(1M).

To Add an Automounter Map to Your NIS Domain

In the /usr/sbin/ypinit script, use a text editor to
add the automounter map to the MASTER_MAPS list, as
follows :

MASTER_MAPS="group.bygid group.byname \ hosts.byaddr bosts.byname netgroup netgroup.byhost \ netgroup.byuser networks.byaddr networks.byname passwd.byname \ passwd.byuid protocols.byname protocols.bynumber rpc.bynumber \ services.byname vhe_list publickey.byname netid.byname mail.byaddr \ mail.aliases auto_master rpc.byname servi.bynp auto_mapname"

In the /var/yp/Makefile file, add the
automounter map to the list of maps that begins with all:,
as follows :

all: passwd group hosts networks rpc services protocols \ netgroup aliases publickey netid vhe_list auto_master \ auto_mapname

In the /var/yp/Makefile file, copy the statement that
begins $(YPDBDIR)/$(DOM)/auto_master.time to the space
below it. Change all occurrences of auto_master to the
name of the map you are adding.

$ (YPDBDIR)/$(DOM)/auto_master.time: $(DIR)/auto_master
 @(sed -e "s/^[ | ]*//g" -e "/^#/d" -e s/#.*$$// <
$(DIR)/auto_master $(CHKPIPE)) |
 $(MAKEDBM) - $(YPDBDIR) /$(DOM)/auto_master;
 @touch $(YPDBDIR)/$(DOM)/auto_master.time;
 @echo "updated auto_master";
 @if [ ! $(NOPUSH) ]; then $(YPPUSH) -d $(DOM) auto_master; fi
 @if [ ! $(NOPUSH) ]; then echo "pushed auto_master"; fi
 
$ (YPDBDIR)/$(DOM)/auto_mapmame.time: $(DIR)/auto_mapname  @(sed -e "s/^[ | ]*//g" -e "/^#/d" -e s/#.*$$// <
$(DIR)/auto_mapname $(CHKPIPE)) |
 $(MAKEDBM) - $(YPDBDIR) /$(DOM)/auto_mapname;
 @touch $(YPDBDIR)/$(DOM)/auto_mapname.time;
 @echo "updated auto_mapname";
 @if [ ! $(NOPUSH) ]; then $(YPPUSH) -d $(DOM) auto_mapname; fi
 @if [ ! $(NOPUSH) ]; then echo "pushed auto_mapname"; fi

In the /var/yp/Makefile
file, copy the statement that begins auto_master: to
the space below it. Change auto_master to auto_mapname,
and change both occurrences of auto_master.time to
auto_mapname.time.

auto_master: @if [ $(NOPUSH) ]; then $(MAKE) $(MFLAGS) -k \ $(YPDBDIR)/$(DOM)/auto_master.time DOM=$(DOM) DIR=$(DIR); \ else $(MAKE) $(MFLAGS) -k $(YPDBDIR)/$(DOM)/auto_master.time \ DOM=$(DOM) DIR=$(DIR) NOPUSH=$(NOPUSH);fi auto_mapname: @if [ $(NOPUSH) ]; then $(MAKE) $(MFLAGS) -k \ $(YPDBDIR)/$(DOM)/auto_mapname.time DOM=$(DOM) DIR=$(DIR); \ else $(MAKE) $(MFLAGS) -k $(YPDBDIR)/$(DOM)/auto_mapname.time \ DOM=$(DOM) DIR=$(DIR) NOPUSH=$(NOPUSH);fi

Issue the following commands to generate the map :

cd /var/yp /usr/ccs/bin/make NOPUSH=1 auto_mapname

If you have slave servers configured in your domain, log into
each slave server and issue the following command to copy the new
map to the slave server :
```
/usr/sbin/ypxfr auto_mapname
```

For more information, see the man page for ypinit(1M),
make(1), ypmake(1M), or ypxfr(1M).

To Remove an Automounter Map from Your NIS
Domain

Log in as root to the NIS master server.
In the /usr/sbin/ypinit script, use a text
editor to remove the map name from the MASTER_MAPS

list.
In the /var/yp/Makefile
file, remove the map from the list of maps that begins with all:.

In the /var/yp/Makefile

file, remove the statement that begins
$(YPDBDIR)/$(DOM)/auto_mapname.time. For
example, if you were removing the auto_home map, you
would remove the following lines :

$ (YPDBDIR)/$(DOM)/auto_home.time: $(DIR)/auto_home @(sed -e "s/^[ | ]*//g" -e "/^#/d" -e s/#.*$$// < $(DIR)/auto_home $(CHKPIPE)) | $(MAKEDBM) - $(YPDBDIR) /$(DOM)/auto_home; @touch $(YPDBDIR)/$(DOM)/auto_home.time; @echo "updated auto_home"; @if [ ! $(NOPUSH) ]; then $(YPPUSH) -d $(DOM) auto_home; fi @if [ ! $(NOPUSH) ]; then echo "pushed auto_home"; fi

In the /var/yp/Makefile
file, remove the statement that begins auto_mapname:.
For example, if you were removing the auto_home map,
you would remove the following lines :

auto_home: @if [ $(NOPUSH) ]; then $(MAKE) $(MFLAGS) -k \ $(YPDBDIR)/$(DOM)/auto_home.time DOM=$(DOM) DIR=$(DIR); \ else $(MAKE) $(MFLAGS) -k $(YPDBDIR)/$(DOM)/auto_home.time \ DOM=$(DOM) DIR=$(DIR) NOPUSH=$(NOPUSH);fi

On the master and on each of the slave servers, remove the
map files, mapname.dir and mapname.pag

from the directory where your maps are stored. The directory is
called /var/yp/domainname, where domainname
is the name of your NIS domain. For example, if you were removing
the auto_home map from the Finance domain,
you would issue the following commands on the master server and on
each of the slave servers :
```
cd /var/yp/Finance rm auto_home.dir auto_home.pag
```

For more information, see the man pages ypinit(1M),
make(1), ypmake(1M), and ypfiles(4).

To Add a Slave Server to Your NIS Domain

Log in as root to the NIS master server.
Issue the following command, where domainname
is the name of the domain to which you want to add the slave server :
```
cd /var/yp/domainname
```
Issue the following command to create an editable ASCII text
file from the ypservers map :
```
/usr/sbin/makedbm -u ypservers > tempfile
```
Use a text editor to add the name of the new server to the
ASCII file, tempfile.
Issue the following command to regenerate the ypservers
map from the ASCII file :
```
/usr/sbin/makedbm tempfile ypservers
```
Log in as root to the new slave server and configure it as an
NIS slave server.

For more information, see the man page for makedbm(1M)
or ypfiles(4).

To Remove a Slave Server from Your NIS Domain

Log in as root to the NIS master server.
Issue the following commands to create an editable ASCII text
file from the ypservers map :
```
cd /var/yp/domainname /usr/sbin/makedbm -u ypservers > tempfile
```
Use a text editor to remove the name of the slave server from
the ASCII file, tempfile.
Issue the following command to regenerate the ypservers
map from the ASCII file :
```
/usr/sbin/makedbm tempfile ypservers
```
Log in as root to the slave server.
Remove all the map files from the map directory, and remove
the map directory. The directory is called /var/yp/domainname,
where domainname is the name of your NIS domain.
For example, if you were removing a slave server from the Finance
domain, you would issue the following commands :
```
cd /var/yp/Finance rm * cd .. rmdir Finance
```
If the slave is not a slave server in any other NIS domain, use a
text editor to set the NIS_SLAVE_SERVER variable to 0
in the /etc/rc.config.d/namesvrs file.
```
NIS_SLAVE_SERVER=0
```
If the slave is not a server
in any other NIS domain, issue the following command to turn off NIS
server capability :
```
/sbin/init.d/nis.server stop
```

For more information, see the man pages makedbm(1M)
and ypfiles(4).

To Query BIND for Host Information After Querying
NIS

This
section tells you how to set up server-side hostname fallback,
which causes your NIS servers to query BIND for host information
after querying NIS. A server will search the NIS hosts

database first, but if the hosts database does not
contain the requested information, the server will query the BIND
name service. The server will return the host information to the
clients through NIS.

Configure your NIS servers as BIND name servers, or install
an /etc/resolve.conf file on each server that allows it
to query a BIND name server. for more information.
On the NIS master server, in the /var/yp/Makefile
file, set the B variable to -b, as
follows :
```
B=-b
```
Issue the following command on the master server to change
the modification time on /etc/hosts so that make
will regenerate the hosts database :
```
/usr/bin/touch /etc/hosts
```
Issue the following commands to
regenerate the NIS maps on the master server and push them to the
NIS slave servers :
```
cd /var/yp /usr/ccs/bin/make
```
On all the NIS servers in your domain, change the hosts
line in the /etc/nsswitch.conf file to the
following :
```
hosts: nis dns files
```

Hewlett-Packard recommends that you use the Name Service Switch on
your NIS clients instead of server-side hostname fallback. However,
if your NIS clients are PCs that do not have a feature like the Name
Service Switch, use the server-side hostname fallback described in
this section if you want to force BIND lookups after NIS lookups.

To Use NIS With Short File Names

Make sure the first 14 characters of your domain name uniquely
identify your domain among the other NIS domains in your network.
If you plan to use NIS to manage your automounter maps, keep
the automounter map names to 10 characters or fewer.
Log in as root to the NIS master server.
In the /var/yp/Makefile file, uncomment all the
lines between START OF EXAMPLE and
```
END OF EXAMPLE
```
. (Remove the sharp sign [#] from the beginning of
each line.) Do not uncomment the START OF EXAMPLE and
END OF EXAMPLE lines.
In the /var/yp/Makefile file, delete everything
after the END OF EXAMPLE line.

This procedure causes your NIS master server to use HP's
proprietary ypmake script instead of the Makefile.
The Makefile does not support short filenames, but

ypmake does. Type man 1M ypmake at the
HP-UX prompt for more information.