broker_allup man page

SYNOPSIS

       broker_allup [-hV] [-o filename]

DESCRIPTION

       The broker_allup utility is a "super" server that is  used
       to house the CPU Broker's shared libraries and their CORBA
       objects.  By default, the server  only  exports  a  single
       object  of  IDL  type edu::utah::pces::Allup.  The user is
       then expected to use this interface to load  each  library
       and interact with it as they need.  Of course, this can be
       tedious so the CPU Broker includes a  shell  script,  bro-
       ker_allup_default(1),  that starts a server and constructs
       a default configuration of objects.

       The set of libraries included with the  Broker  is  listed
       below.  As always, cbhey's "getsuites" command can be used
       to get the online documentation for each library.

       libcpu-broker
              Contains the manager class and, if TimeSys Linux is
              available,  a  real  time  task class that uses the
              Resource Kernel.

       libpolicies
              Contains the strict-policy class that implements  a
              contention  policy  that  favors  tasks that have a
              higher priority.

       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 factory_library.h(3).

       Available command line options:


       -h     Display a usage message

       -V     Print out a version number.

       -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 it is not given one exter-
       nally.   This is to ensure that the Broker objects will be
       able to handle requests in a timely manner.

EXAMPLES

       To open  a  library  named  "foo"  and  save  its  IOR  in
       "foo.ior".

              [nemo@anemone  /tmp]  cbhey file://allup.ior create
              library with name 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.0.0       2003/11/20 22:38:19        BROKER_ALLUP(1)