GLBD(8)                         Domain/OS BSD                          GLBD(8)




NAME
     glbd - Global Location Broker Daemon

SYNOPSIS
     /etc/ncs/glbd [ -create { -first [ -family family_name ] | -from
     host_name } ] [ -change_family family_name ]

DESCRIPTION
     The Global Location Broker Daemon (glbd), part of the Network Computing
     System (NCS), manages the Global Location Broker (GLB) database.  The GLB
     database stores the locations of NCS-based server programs on a network
     or internet.

     The GLB can be replicated for greater availability of its database.
     Copies of the database can exist on several nodes, with the brokers
     maintaining consistency of the replicated database.  (In an internet, at
     least one glbd must run in each network.) Each replica of the GLB keeps a
     list of all the other GLB replicas.  The drm_admin tool administers the
     replication of the GLB database and of the replica list.

     The GLB supports the DARPA IP and the Domain DDS network protocols.  A
     GLB replica can provide access to its database by both IP and DDS
     clients.  However, when communicating with each other to maintain
     replication of the GLB database, GLBs can use only one protocol family.
     You must choose which address family the GLBs will use.  We recommend
     that you choose IP only if you plan to run GLB replicas on hosts other
     than Apollo systems or if you have an internet in which some routers do
     not support DDS.  In an internet, you must ensure that routing nodes
     support the protocol family used by the GLBs.

     A Local Location Broker Daemon (llbd) must be running on the local node
     when glbd is started.  Typically, both brokers are started at boot time
     from the /etc/rc file.

     If glbd is to communicate via IP protocols, a TCP daemon (tcpd) must also
     be running on the local node; tcpd should be started before llbd.

     See Managing the NCS Location Broker for more information.

     Diagnostic output from glbd is written to the file
     `node_data/system_logs/glb_log.

OPTIONS
     -create   Create a replica of the GLB.  This option creates a GLB
               database in addition to starting a broker process.  It must be
               used with either -first or -from.

     -first    This option must be used with the -create option. Use it to
               create the first replica (i.e., the very first instance) of the
               GLB on your network or internet.

     -family family_name
               This option can be used only in conjunction with the -first
               option.  It specifies the address family that the first GLB
               replica will use to identify itself on the replica list.  Any
               subsequently created replicas must use this family to
               communicate with this replica.  Currently, family_name can be
               either dds or ip.  If this option is not used, the replica will
               be identified on the replica list by its DDS address.

     -from host_name
               This option must be used with the -create option. Use it to
               create additional replicas of the GLB.  A replica of the GLB
               must exist at host_name.  The database and replica list for the
               new replica are initialized from those at host_name.  The
               replica at host_name adds an entry for the new replica to its
               replica list and propagates the entry to the other GLB
               replicas.

               A host_name takes the form family:host, where the host can be
               specified either by its name or by its network address.  For
               example, dds://jeeves, dds:#1234.abcd, ip:bertie, and
               ip:#192.5.5.5 are acceptable hostnames.

               The new replica will use the same address family as host_name
               in identifying itself on the replica list.  For example, if
               host_name is an IP address, the new replica will be listed by
               its IP address on the replica list.

     -change_family family_name
               This option should be used only when the protocol family of all
               GLB replicas is being changed.  Currently, family_name can be
               either dds or ip.  For a procedure to change the protocol
               family, see the release document for the current version of the
               operating system.

EXAMPLES
     Initialize and start for the first time the first replica of the GLB on
     this network or internet:

     $ /etc/server /etc/ncs/glbd -create -first -family dds &


     Start for the first time a subsequent replica of the GLB, initializing
     its database from host //jeeves:

     $ /etc/server /etc/ncs/glbd -create -from dds://jeeves &


     Restart an existing replica of the GLB:

     $ /etc/server /etc/ncs/glbd &


     Restart an existing replica of the GLB on remote host //bertie:

     $ crp -on //bertie /etc/server //bertie/etc/ncs/glbd &


SEE ALSO
     drm_admin(8), lb_admin(8), llbd(8), Managing the NCS Location Broker.