rpcbind(8)


NAME

     rpcbind --- universal addresses to RPC program number mapper

SYNOPSIS

     rpcbind [-adhiLls]

DESCRIPTION

     The rpcbind utility is a server that converts RPC program numbers into
     universal addresses.  It must be running on the host to be able to make
     RPC calls on a server on that machine.

     When an RPC service is started, it tells rpcbind the address at which it
     is listening, and the RPC program numbers it is prepared to serve.  When
     a client wishes to make an RPC call to a given program number, it first
     contacts rpcbind on the server machine to determine the address where RPC
     requests should be sent.

     The rpcbind utility should be started before any other RPC service.
     Normally, standard RPC servers are started by port monitors, so rpcbind
     must be started before port monitors are invoked.

     When rpcbind is started, it checks that certain name-to-address
     translation-calls function correctly.  If they fail, the network
     configuration databases may be corrupt.  Since RPC services cannot
     function correctly in this situation, rpcbind reports the condition and
     terminates.

     The rpcbind utility can only be started by the super-user.

OPTIONS

     -a      When debugging (-d), do an abort on errors.

     -d      Run in debug mode.  In this mode, rpcbind will log additional
         information during operation, and will abort on certain errors if
         -a is also specified.  With this option, the name-to-address
         translation consistency checks are shown in detail.

     -f      Do not fork and become a background process.

     -h      Specify specific IP addresses to bind to for UDP requests.  This
         option may be specified multiple times and is typically necessary
         when running on a multi-homed host.  If no -h option is
         specified, rpcbind will bind to INADDR_ANY, which could lead to
         problems on a multi-homed host due to rpcbind returning a UDP
         packet from a different IP address than it was sent to.  Note
         that when specifying IP addresses with -h, rpcbind will
         automatically add 127.0.0.1 and if IPv6 is enabled, ::1 to the
         list.

     -i      "Insecure" mode.  Allow calls to SET and UNSET from any host.
         Normally rpcbind accepts these requests only from the loopback
         interface for security reasons.  This change is necessary for
         programs that were compiled with earlier versions of the rpc
         library and do not make those requests using the loopback
         interface.

     -l      Turn on libwrap connection logging.

     -s      Cause rpcbind to change to the user daemon as soon as possible.
         This causes rpcbind to use non-privileged ports for outgoing
         connections, preventing non-privileged clients from using rpcbind
         to connect to services from a privileged port.

     -w      Cause rpcbind to do a "warm start" by read a state file when
         rpcbind starts up. The state file is created when rpcbind
         terminates.

NOTES

     All RPC servers must be restarted if rpcbind is restarted.

SEE ALSO

     rpcinfo(7)

LINUX PORT

     Aurelien Charbon <aurelien.charbon@bull.net>


More Linux Commands

manpages/glutSolidOctahedron.3.html
glutSolidOctahedron(3) - render a solid or wireframe octahed
glutSolidOctahedron and glutWireOctahedron render a solid or wireframe octahedron respectively centered at the modeling coordinates origin with a radius of 1.0.

manpages/sgetspent_r.3.html
sgetspent_r(3) - get shadow password file entry (Man Page)
Long ago it was considered safe to have encrypted passwords openly visible in the password file. When computers got faster and people got more security-consciou

manpages/newsgroups.5.html
newsgroups(5) - List of newsgroups and their short descripti
ENCODING OF THE DESCRIPTIONS MINIMAL NEWSGROUPS FILE HISTORY SEE ALSO NAME newsgroups - List of newsgroups and their short descriptions DESCRIPTION The file pat

manpages/lexgrog.1.html
lexgrog(1) - parse header information in man pages (ManPage)
lexgrog is an implementation of the traditional groff guess utility in lex. It reads the list of files on its command line as either man page source files or pr

manpages/ttyname.3.html
ttyname(3) - return name of a terminal - Linux manual page
The function ttyname() returns a pointer to the null-terminated pathname of the terminal device that is open on the file descriptor fd, or NULL on error (for ex

manpages/Tk_GetPixels.3.html
Tk_GetPixels(3) - translate between strings and screen units
These procedures take as argument a specification of distance on the screen (objPtr or string) and compute the corresponding distance either in integer pixels o

manpages/glMapGrid2d.3gl.html
glMapGrid2d(3gl) - define a one- or two-dimensional mesh....
glMapGrid and glEvalMesh are used together to efficiently generate and evaluate a series of evenly-spaced map domain values. glEvalMesh steps through the intege

manpages/Memoize::ExpireTest.3pm.html
Memoize::ExpireTest(3pm) - test for Memoize expiration seman
This module is just for testing expiration semantics. Its not a very good example of how to write an expiration module. If you are looking for an example, I rec

manpages/gnutls_x509_crt_get_proxy.3.html
gnutls_x509_crt_get_proxy(3) - API function - Linux man page
This function will get information from a proxy certificate. It reads the ProxyCertInfo X.509 extension (1.3.6.1.5.5.7.1.14). RETURNS On success, GNUTLS_E_SUCCE

manpages/XkbKeySymEntry.3.html
XkbKeySymEntry(3) - Returns the keysym corresponding to shif
XkbKeySymEntry.3 - The key width and number of groups associated with a key are used to form a small two-dimensional array of KeySyms for a key. This array may

manpages/TYPE_INTEGER.3form.html
TYPE_INTEGER(3form) - form system global variables (ManPage)
These are building blocks for the form library, defining fields that can be created using set_fieldtype(3X). Each provides functions for field- and character-va

manpages/Tcl_DeleteEvents.3.html
Tcl_DeleteEvents(3) - the event queue and notifier interface
The interfaces described here are used to customize the Tcl event loop. The two most common customizations are to add new sources of events and to merge Tcls ev





We can't live, work or learn in freedom unless the software we use is free.