Used by the host object to "push" accounting information back to the legion_get_accounting_info tool (page 57). It is only used by the host object.
Start the Application package's security. This command is automatically run when you run legion_init_Apps (page 67).
Start the Extra package's security. This command is automatically run when you run legion_init_Extra (page 67).
Start the HPC package's security. This command is automatically run when you run legion_init_HPC (page 67).
Initiate the SDK package. This command is automatically run when you run legion_initialize (page 39).
Start the SDK package's security. This command is automatically run when you run legion_init_security (page 67).
Backend script for legion_make (page 73). The Legion admin installs this tool as a class, usually in context space in /class, /class/HPC, or /class/SDK. Installed using legion_register_program.
This tool is the actual binary for the Legion MPLC compiler and is called by the legion_mplc script (page 75). It is responsible for parsing an MPL code and generating the appropriate C++ code.
legion_native_mpich_wrapper legion_native_mpiibm_wrapper legion_native_mpisgi_wrapper legion_native_mpiultra_wrapper
Site-specific scripts used to determine how to start native MPI jobs at that site. The Legion admin installs the appropriate tool when he or she runs legion_native_mpi_config_host for the host object running at that site.
This tool tells whether or not a specific Legion user can run on a specific host. If a blank string is returned, then the Legion user cannot run on that machine. If a non-blank string is returned the string represents a Unix/Windows user name, and the legion user runs as that Unix/Windows user on that machine.
A debugging tool for contacting a specified object. Used for internal debugging. If the tool cannot contact the object, it tries to contact the relevant host and class hierarchy to find the cause of the problem.
These three scripts are used for virtual hosts: they sit on the physical host and are called by the virtual host object. Please see section 14.0 in the System Administrator Manual.
This is a wrapper used to manage a long-running process. If the process it is managing dies with a non-zero exit status, or is killed, the wrapper will automatically restart its child. If the child exits with an exit status of zero, the wrapper terminates. If the wrapper receives a SIGINT or a SIGHUP, it passes the signal along to the child and exits.