ypxfrd (8) - Linux Manuals
ypxfrd: NIS map transfer server
rpc.ypxfrd - NIS map transfer server
path] [-p port] [--debug] [-f|--foreground]
- /usr/sbin/rpc.ypxfrd --version
The rpc.ypxfrd server speeds up the transfer process by allowing NIS slave servers to simply copy the master servers map files rather than building their own from scratch. rpc.ypxfrd uses an RPC-based file transfer protocol.
If the on-disk format of the database on both machines is not the same, rpc.ypxfrd will refuse to send the data and ypxfr will fallback to yp_all() and fetch every single entry alone.
rpc.ypxfrd could be started by inetd. But since it starts very slowly, it should be started after ypserv from /etc/init.d/ypxfrd.
It is possible to pass OPTIONS to rpc.ypxfrd using the environment variable YPXFRD_ARGS and this variable can be set in /etc/sysconfig/network.
- Causes the server to run in debugging mode. In debug mode, the server does not background itself and prints extra status messages to stderr for each request that it revceives.
rpc.ypxfrd is using this directory instead of /var/yp.
rpc.ypxfrd will bind itself to this port, which makes it possible to have a router filter packets to the NIS ports. This can restricted the access to the NIS server from hosts on the Internet.
- Prints the version number
- will not put itself into background.
rpc.ypxfrd uses the same functions for checking a host as ypserv. At first, rpc.ypxfrd will check a request from an address with /var/yp/securenets or the tcp wrapper. If the host is allowed to connect to the server, rpc.ypxfrd will uses the rules from /etc/ypserv.conf to check the requested map. If a mapname doesn't match a rule, rpc.ypxfrd will look for the YP_SECURE key in the map. If it exists, rpc.ypxfrd will only allow requests on a reserved port.
The FreeBSD ypxfrd protocol is not compatible with that used by SunOS. This is unfortunate but unavoidable: SUNs protocol is not freely available, and even if it were it would probably not be useful since the SunOS NIS v2 implementation uses the original ndbm package for its map databases whereas the other implementation uses GNU DBM or Berkeley DB. These packages uses vastly different file formats. Furthermore, ndbm and gdbm are byte-order and word width sensitive and not very smart about it, meaning that a gdbm or ndbm database created on a big endian or 64bit system cannot be read on a little endian or 32bit system. The FreeBSD ypxfrd protocol checks, if both, master and slave, uses the same database packages and, if necessary, the byte order of the system.
- Configuration file for options and access rights
- Configuration file for access rights
- Setting additional arguments to rpc.ypxfrd.
ypxfrd protocol and FreeBSD Implementation: Bill Paul <wpaul [at] ctr.columbia.edu>
Linux Implementation: Thorsten Kukuk <kukuk [at] linux-nis.org>