lb_admin(1ncs)lb_admin(1ncs)Namelb_admin - Location Broker Administrative Tool
/etc/ncs/lb_admin [ -version ] [ -nq]
The tool monitors and administers the registrations of DECrpc-based
servers in Global Local Broker (GLB) or Local Location Broker (LLB)
databases. A server registers Universal Unique Identifiers (UUIDs)
specifying an object, a type, and an interface, along with a socket
address specifying its location. A client can locate servers by issu‐
ing lookup requests to GLBs and LLBs.
In accepting input or displaying output, uses either character strings
or descriptive textual names to identify objects, types, and inter‐
faces. A character string directly represents the data in a UUID in
the following format:
where each n is a hexadecimal digit.
With you examine or modify only one database at a time, referred to as
the current database. The command selects the type of Location Broker
database, GLB or LLB. The command selects the host whose LLB database
is to be accessed.
Information about individual command interfaces is available through
Options-nq Do not query for verification of wildcard expan‐
sions in operations.
-version Display the version of the Network Computing Kernel
(NCK) that this belongs to, but do not start the
tool. (NCK is part of the Network Computing System
(NCS) on which DECrpc is based.)
In the descriptions of and the object, type, and interface arguments
can be either character strings representing UUIDs or textual names
corresponding to UUIDs, as described earlier.
In the descriptions of and the location argument is a string in the
format family:host[port], where family is an address family, host is a
host name, and port is a port number. The only value for family is ip.
You can use a leading number sign (#) to indicate that a host name is
in the standard numeric form. For example, ip:vienna, and
ip:#18.104.22.168 are both acceptable location specifiers.
Find and delete obsolete entries in the current database.
When you issue the command, attempts to contact each server
registered in the database. If the server does not respond,
tries to look up its registration in the LLB database at the
host where the server is located, tells you the result of
this lookup, and asks whether you want to delete the entry.
If a server responds, but its UUIDs do not match the entry in
the database, tells you this result and asks whether you want
to delete the entry, even if you used the -nq option to
There are two situations in which it is likely that a data‐
base entry should be deleted:
· The server does not respond, succeeds in contacting
the LLB at the host where the server is located, and
the server is not registered with that LLB. The
server is probably no longer running.
· A server responds, but its UUIDs do not match the
entry in the database. The server that responded is
not the one that registered the entry.
Entries that meet either of these conditions are probably
safe to delete and are considered eligible for automatic
deletion (described in the next paragraph). In other situa‐
tions, it is best not to delete the entry unless you can ver‐
ify directly that the server is not running (for example, by
listing the processes running on its host).
When the command asks whether you want to delete an entry,
choose one of the following responses:
Delete the entry.
n[o] Leave the entry intact in the current database.
g[o] Invoke automatic deletion, in which all eligible entries
(see the previous paragraph) are deleted and all ineli‐
gible entries are left intact, without your being
queried, until all entries have been checked.
Terminate the operation.
Display a description of the specified command or, if
specified, list all of the commands.
Look up and display all entries with matching object,
interface fields in the current database. Use the letter l
to list all of the entries in the database. You can use
asterisks as wildcards for any of the arguments. If all the
arguments are wildcards, or if no arguments are given, dis‐
plays the entire database.
Exit the session.
Add the specified entry to the current database. You
can use an
asterisk to represent the nil UUID in the object, type, and
The annotation is a string of up to 64 characters annotating
the entry. Use double quotation marks (" ") to delimit a
string that contains a space or contains no characters. To
embed a double quotation mark in the string, precede it with
a backslash (\).
The flag is either local (the default) or global, indicating
whether the entry should be marked for local registration
only or for registration in both the LLB and the GLB data‐
bases. The flag is a field that is stored with the entry; it
does not affect where the entry is registered. The and com‐
mands select the particular LLB or GLB database for registra‐
Set the host for the current LLB or GLB. If you specify global as
the broker_switch, sets the current GLB; otherwise, it sets
the current LLB. The host is a location specifier as
described earlier, but the [port] portion is ignored and can
Issue the command, not the command, to determine whether sub‐
sequent operations will access the LLB or the GLB.
Set the timeout period used by
for all of its operations. With an argument of short or
long, sets the timeout accordingly. With no argument, it
displays the current timeout value.
Delete the specified entry from the current database.
You can use an asterisk as a wildcard in the object, type,
and interface fields to match any value for the field.
Unless you suppress queries by specifying the -nq option of
asks you whether to delete each matching entry. Choose one
of the following responses:
Delete the entry.
n[o] Leave the entry in the database.
g[o] Delete all remaining database entries that match, with‐
out your being queried.
Terminate the operation, without deleting any more
Select the type of database that subsequent operations
will access, GLB
or LLB. The broker_switch is either global or local. If you
do not supply a broker_switch, tells whether the current
database is global or local.
Use to select the host whose GLB or LLB is to be accessed.
See Alsollbd(8ncs), nrglbd(8ncs)
Guide to the Location Broker