Legion 1.6 Basic User Manual
Before you start
1.0 Introduction
- 1.1 About this manual
- 1.2 Style conventions
- 1.3 About Legion
Getting started
2.0 Setting up and logging in
- 2.1 Preparing your Legion environment
- 2.2 Logging in to a Legion system
2.2.1 Logging in as a user- 2.2.2 Changing your password
- 2.2.3 About object permissions
- 2.2.4 Checking your log in status
- 2.2.5 Logging out
- 2.2.6 Using Legion in a Kerberos environment
Context space
3.0 An introduction to Legion context space
4.0 The GUI
- 4.1 Installing the GUI in Windows 95
- 4.2 Running the GUI in Windows95
- 4.3 Running the GUI in a Unix environment
- 4.4 The main GUI window
- 4.5 View windows
- 4.6 The startup view window
- 4.7 Main menu commands
- 4.7.1 File
- 4.7.2 View
- 4.7.3 Edit
- 4.8 Context space vs. the GUI cache
5.0 Context space
- 5.1 Legion object names
- 5.2 About the LOID
- 5.3 Organizing context space
6.0 Working in context space
- 6.1 View a context's contents
- 6.2 Looking up an object's LOID
- 6.3 Create a new context
- 6.4 Changing the working context
- 6.5 Checking the current working context/A>
- 6.6 Assigning alternate names to existing contexts
- 6.7 Assigning a context name to a LOID
- 6.8 Renaming an object
- 6.9 Listing an object's names
- 6.10 Removing names and objects
- 6.11 Using the same name in different contexts
- 6.12 Copying a local file to a Legion file object
- 6.13 Copying a Legion file object
- 6.14 Viewing a file object's contents
- 6.15 Importing a local Unix tree
- 6.16 Link a directory to context space
7.0 Host and vault objects
- 7.1 What is a host object and vault object?
- 7.2 About the bootstrap host and vault
- 7.3 Creating objects on new hosts
- 7.4 Controlling instance placement on hosts and vaults
Running applications
8.0 Running a Legion application
9.0 PVM
- 9.1 Core PVM interface
- 9.2 Tids & LOIDs
- 9.3 Task classes 40
- 9.4 Installing PVM-Legion
- 9.5 Compilation
- 9.6 Registering compiled tasks
- 9.7 Examples
- 9.8 Running a PVM code with the fewest changes
10.0 MPI
- 10.1 Task classes
- 10.2 Installing Legion MPI
- 10.3 Compilation
- 10.4 Register compiled tasks
- 10.5 Running the MPI application
- 10.6 Example
- 10.7 Accessing files in programs using MPI
- 10.8 Scheduling MPI processes
- 10.9 Debugging support
- 10.10 Checkpointing support
- 10.10.1 Example
- 10.10.2 API (C & Fortran)
- 10.10.3 Running the above example
- 10.10.4 Recovering from failure
- 10.10.5 Restarting application
- 10.10.6 Compiling/makefile
- 10.10.7 Another example
- 10.10.8 Limitations
- 10.11 Functions supported
- 10.12 Running an MPI code with the fewest changes
11.0 Executing remote programs
- 11.1 Introduction
- 11.2 Compatible and non-compatible programs
- 11.3 Registering non-Legion-compatible programs
- 11.4 Registering Legion-compatible programs
- 11.5 Running a remote program
- 11.6 Converting a C/C++ program
- 11.7 Summary
- 11.8 Running a remote program from the GUI
12.0 Replaying and debugging Legion applications
- 12.1 Sample record and replay
Appendices
A-1 Sample makefile
A-2 About Legion tty objects
- A-2.1 Simple tty management
- A-2.2 Complex tty management
A-3 Alphabetical list of Legion commands
A-4 Subject listing of Legion commands
- A-4.1 Calls on objects
- A-4.2 Calls on class objects
- A-4.3 Calls on LegionClass
- A-4.4 Calls on file and context objects
- A-4.5 Start-up and shutdown functions
- A-4.6 Scheduling support
- A-4.7 General functions about the state of the system
- A-4.8 Security
- A-4.9 Application development
- A-4.10 Program support
Getting help
References
Index
The Legion Group
Department of Computer Science
University of Virginia
Charlottesville, VA 22903
legion@virginia.edu
http://legion.virginia.edu/
Copyright © 1993-1999 by the Rector and Visitors of the University of Virginia.
All rights reserved.
Permission is granted to copy and distribute this manual so long as this copyright page accompanies any copies. The Legion system software herein described is intended for research and is available free-of-charge for that purpose. Permission is not granted for distributing the Legion system software outside of your site.
In no event shall the University of Virginia be liable to any party for direct, indirect, special, incidental, or consequential damages arising out of the use of the Legion system software and its documentation.
The University of Virginia specifically disclaims any warranties, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. The software provided hereunder is on an "as is" basis, and the University of Virginia has no obligation to provide maintenance, support, updates, enhancements, or modifications.
This work partially supported by DARPA (Navy) contract # N66001-96-C-8527, DOE grant DE-FD02-96ER25290, DOE contract Sandia LD-9391, Northrup-Grumman (for the DoD HPCMOD/PET program), DOE D459000-16-3C and DARPA (GA) SC H607305A
