portmap(8) [opendarwin man page]
PORTMAP(8) BSD System Manager's Manual PORTMAP(8) NAME
portmap -- RPC program,version to DARPA port mapper SYNOPSIS
portmap [-d] [-v] [-h bindip] 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. Portmap uses hosts_access(5) access control by default. Access control patterns may only reference IP addresses. Normally portmap forks and dissociates itself from the terminal like any other daemon. Portmap then logs errors using syslog(3). The following options are available: -d Prevent portmap from running as a daemon, and causes errors and debugging information to be printed to the standard error output. -v Enable verbose logging of access control checks. -h Specify specific ip addresses to bind to for UDP requests. This option may be specified multiple times and is typically necessary when running portmap on a multi-homed host. If no -h option is specified, portmap will bind to INADDR_ANY, which could lead to prob- lems on a multi-homed host due to portmap returning a udp packet from a different IP address then it was sent to. Note that when specifying ip addresses with -h, portmap will automatically add 127.0.0.1 to the list so you don't have to. SEE ALSO
hosts_access(5), inetd.conf(5), inetd(8), rpcinfo(8) BUGS
If portmap crashes, all servers must be restarted. HISTORY
The portmap command appeared in 4.3BSD 4.3 Berkeley Distribution June 6, 1993 4.3 Berkeley Distribution
Check Out this Related 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