lb_test(1M)

NAME

lb_test − test the Location Broker

SYNOPSIS

/etc/ncs/lb_test [−unreg] [−num entries] [−time seconds]

DESCRIPTION

The lb_test exerciser tests the functionality of the Global Location Broker (GLB) and Local Location Broker (LLB), parts of the Network Computing System (NCS).

lb_test repeatedly registers and looks up entries with the GLB and with the local LLB. It will fail if a GLB or LLB does not exist, is an incorrect version, is inaccessible, or is functioning improperly. The host that runs lb_test must also run the Local Location Broker daemon (llbd) and must be able to reach a Global Location Broker daemon (glbd or nrglbd).

A Location Broker entry contains Universal Unique Identifiers (UUIDs) for an object, the type of the object, and an interface to the object, together with the location of a server exporting the interface. To avoid flooding the GLB and LLB databases, lb_test always uses the same three UUIDs for all registrations.

lb_test loops, making 256 passes. Each iteration of the loop attempts to register a set of entries and look them up. lb_test attempts to unregister the entries when it exits.

You can specify the number of entries that lb_test will register at each iteration and the amount of time that it will wait between iterations, or you can invoke lb_test with no options and use default values.

If lb_test fails, try running the lb_admin tool to access a Global Location Broker; if lb_admin also fails, there is probably a problem in your GLB configuration.

Options

−num entries
Register the specified number of entries. The default for entries is 5.

−time seconds
Sleep for the specified number of seconds between iterations. The default is to not wait at all.

−unreg
Unregister all entries with the lb_test type UUID. After unregistering the entries, lb_test terminates.

Sample Output

This section shows the output that lb_test produces if the Location Broker is operating correctly. Most of the output has been omitted as indicated by the vertical ellipsis dots.

If the hosts and/or the network used in the test are heavily loaded, additional informational messages may be printed. These message are printed when the Remote Procedure Call (RPC) runtime library is recovering from slow transmissions or lost packets.

$ lb_test
Handling 5 registrations with no time delay
Starting test loop...
    Pass 0
    Pass 1
    Pass 2
    Pass 3
    .
    .
    .
    Pass 252
    Pass 253
    Pass 254
    Pass 255
Unregistering...
$

Museum