*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->HP-UX 11i man pages -> rpcbind (1m)              
Title
Content
Arch
Section
 

Contents


 rpcbind(1M)                                                     rpcbind(1M)




 NAME    [Toc]    [Back]
      rpcbind - universal addresses to RPC program number mapper

 SYNOPSIS    [Toc]    [Back]
      rpcbind [-d] [-w]

 DESCRIPTION    [Toc]    [Back]
      rpcbind 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.

      rpcbind 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.

      rpcbind can only be started by the super-user.

    Options    [Toc]    [Back]
      rpcbind recognizes the following options:

           -d        Run in debug mode.  In this mode, rpcbind will not fork
                     when it starts, will print additional information
                     during operation, and will abort on certain errors.
                     With this option, the name-to-address translation
                     consistency checks are shown in detail.

           -w        Do a warm start.  If rpcbind aborts or terminates on
                     SIGINT or SIGTERM, it will write the current list of
                     registered services to /tmp/portmap.file and
                     /tmp/rpcbind.file.  Starting rpcbind with the -w option
                     instructs it to look for these files and start
                     operation with the registrations found in them.  This
                     allows rpcbind to resume operation without requiring
                     all RPC services to be restarted.

 WARNINGS    [Toc]    [Back]
      Terminating rpcbind with SIGKILL will prevent the warm-start files
      from being written.




 Hewlett-Packard Company            - 1 -   HP-UX 11i Version 2: August 2003






 rpcbind(1M)                                                     rpcbind(1M)




      All RPC servers must be restarted if the following occurs: rpcbind
      crashes (or is killed with SIGKILL) and is unable to to write the
      warm-start files; rpcbind is started without the -w option after a
      graceful termination; or, the warm-start files are not found by
      rpcbind.

 AUTHOR    [Toc]    [Back]
      rpcbind was developed by Sun Microsystems, Inc.

 FILES    [Toc]    [Back]
      /tmp/portmap.file

      /tmp/rpcbind.file

 SEE ALSO    [Toc]    [Back]
      rpcinfo(1M), rpcbind(3N).


 Hewlett-Packard Company            - 2 -   HP-UX 11i Version 2: August 2003
[ Back ]
      
      
 Similar pages
Name OS Title
portmap IRIX TCP, UDP port to RPC program number mapper
portmap OpenBSD DARPA port to RPC program number mapper
portmap Tru64 The DARPA port to RPC program number mapper
portmap Linux DARPA port to RPC program number mapper
inet6_rth_segments Tru64 Return the number of segments (addresses) in an IPv6 Routing header
rpc OpenBSD rpc program number database
rpc Tru64 rpc program number database
rpc Linux rpc program number data base
rpc IRIX RPC program number data base
rpc HP-UX rpc program number data base
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service