nrglbd(8ncs)nrglbd(8ncs)Name
nrglbd - non-replicating global location broker (GBL) daemon
Syntax
/etc/ncs/nrglbd [ -version ]
Description
The global location broker (GLB), enables clients to locate servers on a network or internet. The GLB database stores the locations (that
is, the network addresses and port numbers) where server processes are running. The GLB maintains this database and provides access to it.
The daemon should run as a background process. It requires no options or arguments. A Local Location Broker daemon ( ) must be running on
the local host when is started.
You can run only one on a network or internet.
On ULTRIX systems, is typically started by a line in such as the following:
/etc/ncs/nrglbd& echo -n ' nrglbd' > /dev/console
Options-version Display the version of the Network Computing Kernel (NCK) that this belongs to but do not start the daemon. (NCK is part of the
Network Computing System (NCS) on which DECrpc is based.)
Restrictions
This section discusses the procedure to follow if the system running the is taken off-line.
If you restart on the same system and no server on any other system changed state, all things should run as before. If, however, an appli-
cation tries to contact a server that is no longer running or which has different port numbers, the application will fail. The application
also will not see any new server registrations.
If a copy of is not available, you must create an up to date version of the file before restarting To do so, use to query the for registra-
tion data on every system running an DECrpcserver and then use to register all DECrpc servers with the GLB on the new host. Then restart
See Alsolb_admin(1ncs), llbd(8ncs)
Guide to the Location Broker
nrglbd(8ncs)
Check Out this Related Man Page
lb_lookup_interface(3ncs)lb_lookup_interface(3ncs)Name
lb_lookup_interface - look up information about an interface in the Global Location Broker database
Syntax
#include <idl/c/lb.h>
void lb_$lookup_interface(obj_interface, lookup_handle, max_num_results, num_results, results, status)
uuid_$t *obj_interface;
lb_$lookup_handle_t *lookup_handle;
unsigned long max_num_results;
unsigned long * num_results;
lb_$entry_t results[ ];
status_$t *status;
Arguments
obj_interface The UUID of the interface being looked up.
lookup_handle A location in the database. On input, the lookup_handle indicates the location in the database where the search
begins. An input value of lb_$default_lookup_handle specifies that the search will start at the beginning of the data-
base. On return, the lookup_handle indicates the next unsearched part of the database (that is, the point at which the
next search should begin). A return value of lb_$default_lookup_handle indicates that the search reached the end of
the database; any other return value indicates that the search found at most max_num_results matching entries before it
reached the end of the database.
max_num_results The maximum number of entries that can be returned by a single routine. This should be the number of elements in the
results array.
num_results The number of entries that were returned in the results array.
results An array that contains the matching GLB database entries, up to the number specified by the max_num_results parameter.
If the array contains any entries for servers on the local network, those entries appear first.
status The completion status.
Description
The routine returns GLB database entries whose obj_interface fields match the specified interface. It returns information about objects
that can be accessed through that interface.
The routine cannot return more than max_num_results matching entries at a time. The lookup_handle parameter enables you to find all match-
ing entries by doing sequential lookups.
If you use a sequence of lookup routines to find entries in the database, it is possible that the returned results will skip or duplicate
entries. This is because the Location Broker does not prevent modification of the database between lookups, and such modification can
change the locations of entries relative to a lookup_handle value.
It is also possible that the results of a single lookup routine will skip or duplicate entries. This can occur if the size of the results
exceeds the size of an RPC packet (64K bytes).
Examples
The following statement looks up information in the GLB database about a matrix multiplication interface:
lb_$lookup_interface (&matrix_id, &lookup_handle, max_results,
&num_results, &matrix_results, &st);
Diagnostics
This section lists status codes for errors returned by this routine.
lb_$database_invalid
The format of the Location Broker database is out of date. The database may have been created by an old version of the
Location Broker; in this case, delete the out-of-date database and reregister any entries that it contained. The LLB
or GLB that was accessed may be running out-of-date software; in this case, update all Location Brokers to the current
software version.
lb_$database_busy The Location Broker database is currently in use in an incompatible manner.
lb_$not_registered The Location Broker does not have any entries that match the criteria specified in the lookup or unregister routine.
The requested object, type, interface, or combination thereof is not registered in the specified database. If you are
using an or routine specifying an LLB, check that you have specified the correct LLB.
lb_$cant_access The Location Broker cannot access the database. Among the possible reasons:
1. The database does not exist.
2. The database exists, but the Location Broker cannot access it.
lb_$server_unavailable
The Location Broker Client Agent cannot reach the requested GLB or LLB. A communications failure occurred or the bro-
ker was not running.
FilesSee Alsointro(3ncs), lb_lookup_object(3ncs), lb_lookup_range(3ncs), lb_lookup_type(3ncs)lb_lookup_interface(3ncs)