broker_allup man page
SYNOPSIS
broker_allup [-hVf] [-o filename] [-p PID-filename]
DESCRIPTION
The broker_allup utility is a "super" server that is used to dynami-
cally load the CPU Broker's shared libraries and instantiate its CORBA
objects. By default, the server exports a single object that is used
to load shared libraries into the process. Once a library has been
successfully loaded, an IOR is returned that can be used to interact
with the library. For example, creating a "Manager" object is done by
loading the Broker's main library, libcpu-broker, into broker_allup and
using the library object to create the manager. Of course, doing this
all by hand can be tedious, so the CPU Broker includes a shell script,
broker_allup_default(1), that takes care of most of the work for you.
This script starts broker_allup in the background and constructs a
default configuration of objects using the cbhey tool that is included
with the Broker.
The set of libraries included with the Broker is listed below. As
always, cbhey's "getsuites" command can be used to get the online docu-
mentation for each library.
libcpu-broker
Contains the manager class and the base real-time task class.
libpolicies
Contains the following contention policies: StrictPolicy,
WeightedPolicy, and PartitionPolicy.
libdelegates
Contains the basic delegate classes for several Broker objects.
libtask_factories
Contains several real-time task delegate classes that perform
some type of adaptation.
User defined libraries can also be loaded by broker_allup. The only
requirement is that they follow the interface described in fac-
tory_library.h(3).
Available command line options:
-h Display a usage message
-V Print out a version number.
-f Fork into the background after everything is setup.
-p PID-filename
Specify the file name to store the process' ID. By default, no
file is written.
-o filename
Specify the file name for the Allup object's IOR. Default is
"./allup.ior".
RESOURCE RESERVATIONS
When running on TimeSys Linux, broker_allup will create a soft CPU
reservation for itself if it is not given one externally. This is to
ensure that the Broker objects will be able to handle requests in a
timely manner.
EXAMPLES
To start the program in the background and have its IOR written to
"./allup.ior":
[nemo@anemone /tmp] broker_allup -f
To then load a library named "foo" and save its IOR in "foo.ior".
[nemo@anemone /tmp] cbhey file://allup.ior create library with
name /path/to/foo > foo.ior
To create an object using the "foo" library and save its IOR In
"bar.ior".
[nemo@anemone /tmp] cbhey file://foo.ior create bar > bar.ior
SEE ALSO
broker_allup_default(1), cbhey(1), cpubroker(7)
AUTHOR
The Alchemy project at the University of Utah.
NOTES
The Alchemy project can be found on the web at
http://www.cs.utah.edu/flux/alchemy
CPU Broker 1.1.0 2004/03/05 17:07:36 BROKER_ALLUP(1)
Man(1) output converted with
man2html