HP-UX Reference (11i v1 00/12) - 1M System Administration Commands N-Z (vol 4)

__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1m/naaagt.1m
________________________________________________________________
___ ___
y
ypmake(1M) ypmake(1M)
NAME
ypmake - create or rebuild Network Information Service databases
SYNOPSIS
/var/yp/ypmake [DIR=source_directory ] [DOM=NIS_domain ]\
[NOPUSH=1][PWFILE=passwd_file][map [map ...]]
cd /var/yp; make [DIR=source_directory] [DOM=NIS_domain ]\
[NOPUSH=1][PWFILE=passwd_file][map ...]
Remarks
The Network Information Service (NIS) was formerly known as Yellow Pages (yp). Although the name has
changed, the functionality of the service remains the same.
DESCRIPTION
ypmake is a shell script that builds one or more Network Information Service (NIS) maps (databases) on a
master NIS server. If no arguments are specified, ypmake either creates maps if they do not already exist
or rebuilds maps that are not current. These maps are constructed from ASCII files. ypmake then exe-
cutes yppush to notify slave NIS servers of the change and make the slave servers copy the updated maps
to their machines (see yppush(1M)).
If any maps are supplied on the command line, ypmake creates or updates those maps only. Permissible
names for maps are the lenames in
/etc listed under FILES below. In addition, specific maps can be
named, such as
netgroup.byuser
or rpc.bynumber .
The
make command can be used instead of ypmake (see make(1)). The Makefile no longer calls the
ypmake script but now actually constructs the maps. All NIS commands have been modified to use the
Makefile instead of ypmake. The Makefile and ypmake can co-exist, but it is recommended that
you consider using the Makefile which is the standard mechanism for building maps on other vendor’s
machines.
Both the Makefile and ypmake script use four variables:
DIR=source_directory The directory containing the
ASCII source files from which maps are con-
structed.
DIR defaults to /etc.
DOM=NIS_domain Causes ypmake to construct maps for the specified NIS_domain. DOM
defaults to the NIS domain shown by domainname (see domainname(1)).
NOPUSH=1 When non-null (null by default), NOPUSH inhibits copying the new or
updated databases to the slave NIS servers. Only slave NIS servers in the
specified domain receive yppush notification when NOPUSH is null.
NOPUSH=2 Does the same thing as NOPUSH=1 and sends a "clear current map"
request to the local ypserv process.
PWFILE=passwd_file Specifies the full pathname of the ASCII file that ypmake should use when
building the NIS passwd maps. PWFILE defaults to $DIR/passwd .
The order of arguments passed to ypmake is unimportant, but the maps are built or updated in the left-
to-right order provided.
Refer to ypfiles(4) and ypserv(1M) for an overview of Network Information Service.
DIAGNOSTICS
ypmake returns one of the following exit codes upon completion:
0 Normal termination; no problems.
1 One or more unrecognized arguments were passed.
2 The NIS domain name is not set.
3 The subdirectory used to contain maps for a specific NIS domain, /var/yp/domain_name,
does not exist or is not writable.
4 An error was encountered when building at least one of the maps.
5 One or more maps
ASCII files do not exist or are unreadable.
EXAMPLES
Create or rebuild the password databases (both the passwd.byname
and passwd.byuid maps) from
/etc/passwd and use yppush to copy the databases to any slave NIS servers in the default
NIS
HP-UX Release 11i: December 2000 1 Section 1M1077
___
___