.TH RPC.YPXFRD 8 "August 2001" "YP Server" "Reference Manual"

.TH RPC.YPXFRD 8 "February 2006" "YP Server" "Reference Manual"

rpc.ypxfrd \- NIS map transfer server

rpc.ypxfrd \- fast NIS map transfer server

is used for speed up the transfer of very large NIS maps from a NIS

is used to speed up the transfer of very large NIS maps from the NIS

master to the NIS slave server. If a  NIS slave server receives a

master server to NIS slave servers. Generally, if a NIS slave server

message that there is a new map, it will start 

receives a notification to update a map, it will start

for transfering the new map.

to transfer the new map.

will read the contents of a map from the master server using the yp_all() 

will read the contents of a map from the master server using the yp_all()

server speeds up the transfer process by allowing NIS slave servers to

server, in co-operation with the ypxfr client, speeds up the transfer

simply copy the master server's map files rather than building their

process by allowing NIS slave servers to simply copy the master server's

own from scratch.

map files verbatim, rather than building their own from scratch.

could be started by inetd. But since it starts very slowly,

can be started by inetd. But since it starts very slowly,

Causes the server to run in debugging mode. In debug mode, the server 

Causes the server to run in debug mode. In this mode, the server 

for each request that it revceives.

for each request that it receives.

is using this directory instead of /var/yp

will use this directory instead of /var/yp

to the NIS ports. This can restricted the access to the NIS server from

to the NIS ports. This can simplifiy restricting the access to the

hosts on the Internet.

rpc.ypxfrd server from hosts on the Internet.

uses the same functions for checking a host as

uses the same functions for checking a host's permissions as

.B ypserv.

.B ypserv

At first,

does. First,

.B rpc.ypxfrd

.B rpc.ypxfrd

will check a request from an address with 

will check a request from an address with

.B /var/yp/securenets

.BR /var/yp/securenets .

or the tcp wrapper.

will uses the rules from

will use the rules from

will only allow requests on a reserved port.

will only allow requests to a reserved port. Note: this form

of access control only helps if all allowed client hosts are trusted to

prevent unprivileged users from binding to reserved ports.

but unavoidable: Sun's protocol is not freely available, and even if it

but unavoidable: Sun's protocol is not freely available.

were it would probably not be useful since the SunOS NIS v2 implimentation

.LP

uses the original ndbm package for its map databases whereas the other

Even if it were, it would probably not be useful since the SunOS NIS v2

implimentation uses GNU DBM or Berkeley DB. These packages uses vastly 

implementation uses the original ndbm package for its map databases

different file formats. Furthermore, ndbm and gdbm are byte-order sensitive 

whereas other implementations use GNU DBM or Berkeley DB. These

and not very smart about it, meaning that a gdbm or ndbm database created on 

databases use vastly different file formats.

a big endian system can't be read on a little endian system. The FreeBSD

.LP

Furthermore, ndbm and gdbm are sensitive to byte-order and word width,

this means that a gdbm or

ndbm database created on a big endian system can't be read on a little

endian system and vice versa, and such databases cannot be exchanged

across machines with different word width (32 vs. 64 bit) either.

.LP

The FreeBSD

protocol checks, if both, master and slave, uses the same database packages

protocol checks if both master and slave use the same database packages

and, if necessary, the byte order of the system.

and, if necessary, the byte order and word width, of the system.

.SH AUTHOR

.SH AUTHORS

ypxfrd protocol and FreeBSD Implementation: Bill Paul <wpaul@ctr.columbia.edu>

.IP "Bill Paul <wpaul@ctr.columbia.edu>"

.br

ypxfrd protocol and FreeBSD Implementation

Linux Implementation: Thorsten Kukuk <kukuk@suse.de>

.IP "Thorsten Kukuk <kukuk@suse.de>"

Linux implementation

.IP "Matthias Andree <matthias.andree@gmx.de>"

Manual page improvements