Add support for rpc.ypxfrd and document it in the man page.

Also generallize the yp_dbwrite functions a little: allow the caller
to specify certain flags. I need this mostly for some changes to
rpc.yppasswdd to allow in-place updates.

Also change Makefile a little to use the same format as ypserv.

1 files changed, 25 insertions, 1 deletions

diff --git a/libexec/ypxfr/ypxfr.8 b/libexec/ypxfr/ypxfr.8
index 188f22b..285c258 100644
--- a/libexec/ypxfr/ypxfr.8
+++ b/libexec/ypxfr/ypxfr.8
@@ -28,7 +28,7 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.\"	$Id: ypxfr.8,v 1.1.1.1 1995/12/25 03:07:13 wpaul Exp $
+.\"	$Id: ypxfr.8,v 1.3 1996/06/05 04:07:04 wpaul Exp $
 .\"
 .Dd February 5, 1995
 .Dt YPXFR 8
@@ -122,6 +122,30 @@ is invoked without a controlling terminal, e.g. from inside
 it logs all its output using the
 .Xr syslog 3
 facility.
+.Sh NOTES
+The FreeBSD version of
+.Nm ypxfr
+has support for a special map transfer protocol which works in
+conjunction with the FreeBSD
+.Xr rpc.ypxfrd 8
+server. This protocol allows it to transfer raw map database files from
+the NIS master server and can be many times faster than the standard
+transfer method, particularly for very large NIS maps. The
+.Nm ypxfr
+command will check to see if the
+.Xr rpc.ypxfrd 8
+server is registered on the NIS master server and attempt to use
+it if it is present. If it isn't it will fall back to the standard
+transfer method, copying the map contents from
+.Xr ypserv 8
+and creating new maps instead.
+.Pp
+Note that while the FreeBSD ypxfrd protocol is conceptually similar
+to the SunOS ypxfrd protocol, FreeBSD's protocol is not compatible with
+Sun's, therefore it will not work with Sun's ypxfrd server. FreeBSD
+slave systems can still transfer maps from any non-FreeBSD NIS server,
+however they will only be able to take advantage of the faster protocol
+if the master server is also running FreeBSD.
 .Sh OPTIONS
 The following options and flags are supported by
 .Nm ypxfr :