rt_server man page
SYNOPSIS
rt_server [-hV] [-o ior-file] [-m manager-ior] [-P period] [-f run-
time] <-t task-ior|-n name> [compute1 [compute2 ...]]
DESCRIPTION
The rt_server utility exports a CORBA object that generates synthetic
computing load when periodically driven by the rt_client(1) command.
Its primary purpose is to serve as an interesting process that the CPU
Broker can manage. The process communicates with the Broker using the
task object specified by -t or creates its own if -n is used. The
actual amount of CPU it consumes in a given period is determined by the
computeN arguments. These arguments specify a loop of time values that
determine how much of the period it should spend consuming the CPU.
The values can be a number with units (e.g. "60000000us", "60000ms",
"60s", or "1m") or without, in which case it is assumed to be microsec-
onds. When a period completes, it will switch to the next value in the
sequence. The default sequence oscillates between consuming half the
period and a quarter of the period.
Available options:
-h Print out a usage message.
-V Print out a version number.
-o ior-file
The output file for the object's IOR. (Default: ./rtserver.ior)
-m manager-ior
The Broker::Manager IOR for this machine. (Default: file://man-
ager.ior)
-P period
The period of the process. The value can be a number with units
(e.g. "60000000us", "60000ms", "60s", or "1m") or without, in
which case it is assumed to be microseconds. (Default: 1 sec-
ond)
-f run-time
The amount of time to run for. The value can be a number with
units (e.g. "60000000us", "60000ms", "60s", or "1m") or without,
in which case it is assumed to be microseconds. (Default: for-
ever)
-t task-ior
The IOR for the Broker::RealTimeTask that has been created for
this process. This is incompatible with the -n option.
-n name
The name to use when creating a Broker::RealTimeTask for this
process. This is incompatible with the -t option.
EXAMPLES
To start a process with a period of half a second and consumes 100 mil-
liseconds and 125 milliseconds every other period.
[nemo@anemone rbroker] rt_server -n rt1 -P 500ms 100ms 125ms
Now to drive that process we start a client:
[nemo@anemone rbroker] rt_client -P 500ms
SEE ALSO
rt_client(1), rktimes(1), broker_allup(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.2.0 2004/03/08 16:52:53 RT_SERVER(1)
Man(1) output converted with
man2html