portmap(8) [redhat man page]

PORTMAP(8)						    BSD System Manager's Manual 						PORTMAP(8)

NAME

     portmap -- DARPA port to RPC program number mapper

SYNOPSIS

     portmap [-d] [-v]

DESCRIPTION

     Portmap is a server that converts RPC program numbers into DARPA protocol port numbers.  It must be running in order to make RPC calls.

     When an RPC server is started, it will tell portmap what port number it is listening to, and what RPC program numbers it is prepared to
     serve.  When a client wishes to make an RPC call to a given program number, it will first contact portmap on the server machine to determine
     the port number where RPC packets should be sent.

     Portmap must be started before any RPC servers are invoked.

     Normally portmap forks and dissociates itself from the terminal like any other daemon.  Portmap then logs errors using syslog(3).

     Option available:

     -d      (debug) prevents portmap from running as a daemon, and causes errors and debugging information to be printed to the standard error
	     output.

     -v      (verbose) run portmap in verbose mode.

     This portmap version is protected by the tcp_wrapper library. You have to give the clients access to portmap if they should be allowed to use
     it. To allow connects from clients of the .bar.com domain you could use the following line in /etc/hosts.allow:

     portmap: .bar.com

     You have to use the daemon name portmap for the daemon name (even if the binary has a different name). For the client names you can use the
     keyword ALL, IP addresses, hostnames or domain names.

     For further information please have a look at the tcpd((8)), hosts_allow((5)) and hosts_access((5)) manual pages.

SEE ALSO

     xinetd.conf((5)), rpcinfo((8)), pmap_set((8)), pmap_dump((8)), xinetd((8)) tcpd((8)) hosts_access((5)) hosts_options((5))

BUGS

     If portmap crashes, all rpc servers must be restarted.

HISTORY

     The portmap command appeared in BSDBSD 4.3.

4.3 Berkeley Distribution					  March 16, 1991					 4.3 Berkeley Distribution

rpc.statd(8)						      System Manager's Manual						      rpc.statd(8)

NAME

       rpc.statd - NSM status monitor

SYNOPSIS

       /sbin/rpc.statd [-F] [-d] [-?] [-n  name ] [-o  port ] [-p  port ] [-V]

DESCRIPTION

       The  rpc.statd  server implements the NSM (Network Status Monitor) RPC protocol.  This service is somewhat misnomed, since it doesn't actu-
       ally provide active monitoring as one might suspect; instead, NSM implements a reboot notification service. It is  used	by  the  NFS  file
       locking service, rpc.lockd, to implement lock recovery when the NFS server machine crashes and reboots.

   Operation
       For  each  NFS  client  or  server  machine to be monitored, rpc.statd creates a file in /var/lib/nfs/statd/sm.	When starting, it iterates
       through these files and notifies the peer rpc.statd on those machines.

OPTIONS

       -F     By default, rpc.statd forks and puts itself in the background when started. The -F argument tells it to remain  in  the  foreground.
	      This option is mainly for debugging purposes.

       -d     By default, rpc.statd sends logging messages via syslog(3) to system log.  The -d argument forces it to log verbose output to stderr
	      instead. This option is mainly for debugging purposes, and may only be used in conjunction with the -F parameter.

       -n, --name name
	      specify a name for rpc.statd to use as the local hostname. By default, rpc.statd will call gethostname(2) to get the local hostname.
	      Specifying a local hostname may be useful for machines with more than one interfaces.

       -o, --outgoing-port port
	      specify  a  port for rpc.statd to send outgoing status requests from.  By default, rpc.statd will ask portmap(8) to assign it a port
	      number.  As of this writing, there is not a standard port number that portmap always or usually assigns.	Specifying a port  may	be
	      useful when implementing a firewall.

       -p, --port port
	      specify  a port for rpc.statd to listen on.  By default, rpc.statd will ask portmap(8) to assign it a port number.  As of this writ-
	      ing, there is not a standard port number that portmap always or usually assigns.	Specifying a port may be useful when  implementing
	      a firewall.

       -?     Causes rpc.statd to print out command-line help and exit.

       -V     Causes rpc.statd to print out version information and exit.

TCP_WRAPPERS SUPPORT
       This  rpc.statd version is protected by the tcp_wrapper library. You have to give the clients access to rpc.statd if they should be allowed
       to use it. To allow connects from clients of the .bar.com domain you could use the following line in /etc/hosts.allow:

       statd: .bar.com

       You have to use the daemon name statd for the daemon name (even if the binary has a different name).

       For further information please have a look at the tcpd(8) and hosts_access(5) manual pages.

FILES

       /var/lib/nfs/statd/sm/state
       /var/lib/nfs/statd/sm/*
       /var/lib/nfs/statd/sm.bak/*

SEE ALSO

       rpc.nfsd(8), portmap(8)

AUTHORS

       Jeff Uphoff <juphoff@transmeta.com>
       Olaf Kirch <okir@monad.swb.de>
       H.J. Lu <hjl@gnu.org>
       Lon Hohberger <hohberger@missioncriticallinux.com>

								    08 Mar 2001 						      rpc.statd(8)