YPXFR(1M) RISC/os Reference Manual YPXFR(1M)
NAME
ypxfr - transfer NIS map from a NIS server to here
SYNOPSIS
/usr/etc/yp/ypxfr [ -f ] [ -c ] [ -ddomain ] [ -hhost ] [
-sdomain ]
[ -Ctid prog ipadd port ] [ -S ] mapname
DESCRIPTION
ypxfr moves a NIS map in the default domain for the local
host to the local host by making use of normal NIS services.
It creates a temporary map in the directory /etc/yp/domain
(this directory must already exist; domain is the default
domain for the local host), fills it by enumerating the
map's entries, fetches the map parameters (master and order
number), and loads them. It then deletes any old versions
of the map and moves the temporary map to the real mapname.
If run interactively, ypxfr it writes its output to the ter-
minal. However, if it is invoked without a controlling ter-
minal, and if the log file /etc/yp/ypxfr.log exists, it will
append all its output to that file. Since ypxfr is most
often run from the crontab file, or by ypserv, you can use
the log file to retain a record of what was attempted, and
what the results were.
For consistency between servers, ypxfr should be run period-
ically for every map in the NIS data base. Different maps
change at different rates: the services.byname map may not
change for months at a time, for instance, and may therefore
be checked only once a day (in the wee hours). You may know
that mail.aliases or hosts.byname changes several times per
day. In such a case, you may want to check hourly for
updates. A crontab(5) entry can be used to perform periodic
updates automatically. Rather than having a separate cron-
tab entry for each map, you can group comands to update
several maps in a shell script. Examples (mnemonically
named) are in /usr/etc/yp: ypxfr_1perday, ypxfr_2perday,
and ypxfr_1perhour. They can serve as reasonable first
cuts.
Refer to ypfiles(5) and ypserv(1M) for an overview of the
Network Information Service.
OPTIONS
-f Force the transfer to occur even if the version at
the master is not more recent than the local ver-
sion.
-c Do not send a ``Clear current map'' request to the
local ypserv process. Use this flag if ypserv is
not running locally at the time you are running
Printed 11/19/92 Page 1
YPXFR(1M) RISC/os Reference Manual YPXFR(1M)
ypxfr. Otherwise, ypxfr will complain that it
can't talk to the local ypserv, and the transfer
will fail.
-ddomain Specify a domain other than the default domain.
-hhost Get the map from host, regardless of what the map
says the master is. If host is not specified,
ypxfr will ask the NIS service for the name of the
master, and try to get the map from there. host
may be a name or an internet address in the form
a.b.c.d.
-sdomain Specify a source domain from which to transfer a
map that should be the same across domains (such
as the services.byname map).
-Ctid prog ipadd port
This option is only for use by ypserv. When
ypserv invokes ypxfr, it specifies that ypxfr
should call back a yppush process at the host with
IP address ipaddr, registered as program number
prog, listening on port port, and waiting for a
response to transaction tid.
-S This option causes ypxfr to require that the
ypserv server, from which it will obtain the maps
to be transferred, is using ``priviledged'' IP
ports. Since only super-user processes are typi-
cally allowed to use priviledged ports, this
feature adds an extra measure of security to the
transfer. If the map being transferred is a
secure map, ypxfr sets the permissions on the map
to 0600.
FILES
/etc/yp/ypxfr.log log file
/usr/etc/yp/ypxfr_1perday
script to run one transfer per day, for
use with cron(1M)
/usr/etc/yp/ypxfr_2perday
script to run two transfers per day
/usr/etc/yp/ypxfr_1perhour
script for hourly transfers of volatile
maps
/etc/yp/domain NIS domain
SEE ALSO
cron(1M), ypserv(1M), yppush(1M).
crontab(5), ypfiles(5) in the Programmer's Reference Manual.
Page 2 Printed 11/19/92
YPXFR(1M) RISC/os Reference Manual YPXFR(1M)
Network Information Service Service, Chapter 12, in the Sys-
tem Administrator's Guide.
ORIGIN
Sun Microsystems
Printed 11/19/92 Page 3