Attachment 68856 Details for Bug 151520

[patch] general man page overhaul, includes fix for Bug #151226

rpc.ypxfrd.8.patch (text/plain), 5.56 KB, created by Matthias Andree on 2006-02-16 15:52:20 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Matthias Andree

Created: 2006-02-16 15:52:20 UTC

Size: 5.56 KB

patch

obsolete

>--- ./rpc.ypxfrd.8.orig	2006-02-16 16:20:53.000000000 +0100
>+++ ./rpc.ypxfrd.8	2006-02-16 16:43:02.000000000 +0100
>@@ -1,7 +1,7 @@
> .\" -*- nroff -*-
>-.TH RPC.YPXFRD 8 "August 2001" "YP Server" "Reference Manual"
>+.TH RPC.YPXFRD 8 "February 2006" "YP Server" "Reference Manual"
> .SH NAME
>-rpc.ypxfrd \- NIS map transfer server
>+rpc.ypxfrd \- fast NIS map transfer server
> .SH SYNOPSIS
> .B /usr/sbin/rpc.ypxfrd
> [
>@@ -20,70 +20,72 @@
> .SH DESCRIPTION
> .LP
> .B rpc.ypxfrd
>-is used for speed up the transfer of very large NIS maps from a NIS
>-master to the NIS slave server. If a  NIS slave server receives a
>-message that there is a new map, it will start 
>+is used to speed up the transfer of very large NIS maps from the NIS
>+master server to NIS slave servers. Generally, if a NIS slave server
>+receives a notification to update a map, it will start
> .B ypxfr
>-for transfering the new map.
>+to transfer the new map.
> .B ypxfr 
>-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()
> function. This process can take several minutes when there are very large
> maps which have to be stored by the database library.
> .LP
> The
> .B rpc.ypxfrd
>-server speeds up the transfer process by allowing NIS slave servers to
>-simply copy the master server's map files rather than building their
>-own from scratch.
>+server, in co-operation with the ypxfr client, speeds up the transfer
>+process by allowing NIS slave servers to simply copy the master server's
>+map files verbatim, rather than building their own from scratch.
> .B rpc.ypxfrd
> uses an RPC-based file transfer protocol, so that there is no need
> for building a new map.
> 
> .B rpc.ypxfrd
>-could be started by inetd. But since it starts very slowly,
>+can be started by inetd. But since it starts very slowly,
> it should be started after
> .B ypserv
> from /etc/init.d/ypxfrd.
> .SH OPTIONS
> .TP
> .B \-\-debug
>-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 
> does not background itself and prints extra status messages to stderr 
>-for each request that it revceives.
>+for each request that it receives.
> .TP
> .BI \-d " directory"
> .B rpc.ypxfrd
>-is using this directory instead of /var/yp
>+will use this directory instead of /var/yp
> .TP
> .BI \-p " port"
> .B 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.
>+to the NIS ports. This can simplifiy restricting the access to the
>+rpc.ypxfrd server from hosts on the Internet.
> .TP
> .B \-\-version
> Prints the version number
> .SH SECURITY
> .B rpc.ypxfrd
>-uses the same functions for checking a host as
>-.B ypserv.
>-At first,
>-.B rpc.ypxfrd
>-will check a request from an address with 
>-.B /var/yp/securenets
>-or the tcp wrapper.
>+uses the same functions for checking a host's permissions as
>+.B ypserv
>+does. First,
>+.B rpc.ypxfrd
>+will check a request from an address with
>+.BR /var/yp/securenets .
> If the host is allowed to connect to the server, 
> .B rpc.ypxfrd
>-will uses the rules from
>+will use the rules from
> .B /etc/ypserv.conf
> to check the requested map. If a mapname doesn't match a rule, 
> .B rpc.ypxfrd
> will look for the YP_SECURE key in the map. If it exists,
> .B rpc.ypxfrd
>-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.
> .SH FILES
> /etc/ypserv.conf
>+.br
> /var/yp/securenets
> .SH "SEE ALSO"
> .BR ypserv (8),
>@@ -95,18 +97,28 @@
> The FreeBSD
> .B ypxfrd
> protocol is not compatible with that used by SunOS. This is unfortunate
>-but unavoidable: Sun's protocol is not freely available, and even if it
>-were it would probably not be useful since the SunOS NIS v2 implimentation
>-uses the original ndbm package for its map databases whereas the other
>-implimentation uses GNU DBM or Berkeley DB. These packages uses vastly 
>-different file formats. Furthermore, ndbm and gdbm are byte-order sensitive 
>-and not very smart about it, meaning that a gdbm or ndbm database created on 
>-a big endian system can't be read on a little endian system. The FreeBSD
>+but unavoidable: Sun's protocol is not freely available.
>+.LP
>+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 other implementations use GNU DBM or Berkeley DB. These
>+databases use vastly different file formats.
>+.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
> .B ypxfrd
>-protocol checks, if both, master and slave, uses the same database packages
>-and, if necessary, the byte order of the system.
>+protocol checks if both master and slave use the same database packages
>+and, if necessary, the byte order and word width, of the system.
> .LP
>-.SH AUTHOR
>-ypxfrd protocol and FreeBSD Implementation: Bill Paul <wpaul@ctr.columbia.edu>
>-.br
>-Linux Implementation: Thorsten Kukuk <kukuk@suse.de>
>+.SH AUTHORS
>+.IP "Bill Paul <wpaul@ctr.columbia.edu>"
>+ypxfrd protocol and FreeBSD Implementation
>+.IP "Thorsten Kukuk <kukuk@suse.de>"
>+Linux implementation
>+.IP "Matthias Andree <matthias.andree@gmx.de>"
>+Manual page improvements

Actions: View | Diff

Attachments on bug 151520: 68856 | 68858