1RPC.YPXFRD(8)                NIS Reference Manual                RPC.YPXFRD(8)
2
3
4

NAME

6       rpc.ypxfrd - NIS map transfer server
7

SYNOPSIS

9       /usr/sbin/rpc.ypxfrd [-d path] [-p port] [--debug]
10
11       /usr/sbin/rpc.ypxfrd --version
12

DESCRIPTION

14       rpc.ypxfrd is used for speed up the transfer of very large NIS maps
15       from a NIS master to the NIS slave server. If a NIS slave server
16       receives a message that there is a new map, it will start ypxfr for
17       transfering the new map.  ypxfr will read the contents of a map from
18       the master server using the yp_all() function.
19
20       The rpc.ypxfrd server speeds up the transfer process by allowing NIS
21       slave servers to simply copy the master servers map files rather than
22       building their own from scratch.  rpc.ypxfrd uses an RPC-based file
23       transfer protocol.
24
25       If the on-disk format of the database on both machines is not the same,
26       rpc.ypxfrd will refuse to send the data and ypxfr will fallback to
27       yp_all() and fetch every single entry alone.
28
29       rpc.ypxfrd could be started by inetd. But since it starts very slowly,
30       it should be started after ypserv from /etc/init.d/ypxfrd.
31

OPTIONS

33       --debug
34           Causes the server to run in debugging mode. In debug mode, the
35           server does not background itself and prints extra status messages
36           to stderr for each request that it revceives.
37
38       -d path
39
40           rpc.ypxfrd is using this directory instead of /var/yp.
41
42       -p port
43
44           rpc.ypxfrd will bind itself to this port, which makes it possible
45           to have a router filter packets to the NIS ports. This can
46           restricted the access to the NIS server from hosts on the Internet.
47
48       --version
49           Prints the version number
50

SECURITY

52       rpc.ypxfrd uses the same functions for checking a host as ypserv. At
53       first, rpc.ypxfrd will check a request from an address with
54       /var/yp/securenets or the tcp wrapper. If the host is allowed to
55       connect to the server, rpc.ypxfrd will uses the rules from
56       /etc/ypserv.conf to check the requested map. If a mapname doesn´t match
57       a rule, rpc.ypxfrd will look for the YP_SECURE key in the map. If it
58       exists, rpc.ypxfrd will only allow requests on a reserved port.
59

NOTES

61       The FreeBSD ypxfrd protocol is not compatible with that used by SunOS.
62       This is unfortunate but unavoidable: SUNs protocol is not freely
63       available, and even if it were it would probably not be useful since
64       the SunOS NIS v2 implementation uses the original ndbm package for its
65       map databases whereas the other implementation uses GNU DBM or Berkeley
66       DB. These packages uses vastly different file formats. Furthermore,
67       ndbm and gdbm are byte-order and word width sensitive and not very
68       smart about it, meaning that a gdbm or ndbm database created on a big
69       endian or 64bit system cannot be read on a little endian or 32bit
70       system. The FreeBSD ypxfrd protocol checks, if both, master and slave,
71       uses the same database packages and, if necessary, the byte order of
72       the system.
73

FILES

75       /etc/ypserv.conf
76           Configuration file for options and access rights
77
78       /var/yp/securenets
79           Configuration file for access rights
80

SEE ALSO

82       ypserv(8), makedbm(8), yppush(8), ypxfr(8)
83

AUTHOR

85       ypxfrd protocol and FreeBSD Implementation: Bill Paul
86       <wpaul@ctr.columbia.edu>
87
88       Linux Implementation: Thorsten Kukuk <kukuk@linux-nis.org>
89
90
91
92NIS Reference Manual              04/15/2008                     RPC.YPXFRD(8)