2.5 Start-up and shutdown functionslegion_add_host_account {-l <host object LOID> | [-c] <host object context path>} {[-f <mapping file name>] | [<Unix user id> [-l <owner LOID> | -c <owner context path>]]} [-debug] [-help] This command is used on PCD host objects. Adds a mapping between a Legion account and a Unix account and adds this mapping to a PCD host object's list of available accounts. The user's Unix user id is named in the <Unix user id> parameter. The host object is named in the <host object LOID>/<host object context path> parameter. The user's Legion user id can be given in the <owner LOID>/<owner context path> parameter or listed in the mapping file. The following options are supported: There are two ways to add host accounts: directly from the command line or, via the -f flag, with a mapping file. A mapping file contains a list of Unix-Legion account mappings. This file contains a list of Unix user ids and any corresponding Legion user ids. If no Legion account is named, the account will be treated as a guest account. There is no limit on the number of mappings that can be listed. A sample mapping file is below.
legion_create_class [[-c] <context path>] [-sc <scheduler context path>] [-sl <scheduler LOID>] [-debug] [-help] Creates a new instance of class VanillaMetaClass. The object will be placed in the current working context, unless specified with the -c flag. The following options are supported:
legion_destroy_host [-v] {[-c] <host context path> | -l <host LOID>} [-debug] [-help] Destroy a given host object. All contexts objects on that host will be destroyed and all active objects will be deactivated. Legion will automatically search your context space and remove any dangling context names for the host object. Optional parameters do the following:
legion_destroy_vault {[-c] <vault context path> | -l <vault LOID>} [-debug] [-help] Destroy a given vault object. Legion will attempt to move all of the vault's current OPRs off of the vault object and then destroy the vault object. If any OPRs cannot be successfully moved the process will abort and an error message will be displayed. The following options are supported:
legion_initialize [-debug] [-help] Populates the Legion system with basic classes and implementations. This command should be run after a Legion system is started for the first time (using legion_startup). On subsequent activations of the system, the state created by this utility will already exist, so this command should not be run again. The following options are supported:
legion_list_host_accounts {-l <host object LOID> | [-c] <host object context path>} <user id> [-debug] [-help] This command is used on PCD host objects. It lists the available accounts on a host object. If no host object argument is provided, your current host object will be used as a default. The following options are supported:
legion_make_setup_script [-o <script basename>] [-OPR <OPR dir name>] [-L <$LEGION dir name>] [-debug] [-help] Generates a Legion setup script for your system. This script sets the environment variables for Legion users. The following options are supported:
legion_print_config [-debug] [-help] Prints the "well-known" binding for LegionClass in the current Legion configuration. The following options are supported:
legion_remove_host_account [-l <host object LOID> | [-c] <host object context path>] [-debug] [-help] This command is used on PCD host objects. It removes one or more account mappings from the host object's list of available accounts. The <user id> parameter is the user's Unix user id. If no host is named in the <host object LOID>/<host object context path> parameter, your current host object will be the default host. The following options are supported:
legion_setup_state [-i] [-debug] [-help] Creates OPRs for the basic Legion system objects. This script should be run when starting a Legion system for the first time. The following optional parameters are supported:
legion_shutdown [-local] [-f] [-i] [-debug] [-help] Shuts down a running Legion system, preserving the state of all objects for subsequent reactivation of the system. Optional parameters allow users to shut down individual hosts and to specify an interactive shutdown. Optional parameters do the following:
legion_shutdown_class {[-c] <class context name> | -l <class LOID>} [-debug] [-help] Deactivates the class object named in <class LOID> or <context path> and all of its instances. This command operates recursively: if applied to a metaclass, for example, it would deactivate the metaclass, all of its class instances, all of their instances, etc. The following options are supported:
legion_starthost [-L <$LEGION>] [-O <$LEGION_OPR>] [-A <$LEGION_ARCH>] [-B <path>] [-N <context name>] [-U <user id>] [-C <host class>] <new host name> [<compatible vault list>] [-debug] [-help] Creates a new host object on the specified <new host name>, using the legion_create_object_r command (automatically invoked on the host class). The <new host name> is the host's DNS name. The legion_starthost command selects the following default values for the new object: <$LEGION_OPA> = $LEGION_OPR/Host-$HOST.OPA You can run Legion commands on a remote host using rsh or ssh, once you set the proper environment variables. For sh, ksh, or bash, use: Optional parameters do the following:
legion_startup [-local] [-debug] [-help] Starts up basic Legion services. The following optional parameters are supported:
legion_startvault [-L <$LEGION>] [-O <$LEGION_OPR>] [-A <$LEGION_ARCH>] [-N <context name>] [-U <user id>] [-C <vault class>] <host name> [<compatible host list>] [-debug] [-help] Creates a new vault object on the specified <host name>, using the legion_create_object_r command (automatically invoked on the host class) (page 13). The <host name> is the host's DNS name. You can run Legion commands on a remote host using rsh or ssh, once you set the proper environment variables. For sh, ksh, or bash, use: The following optional parameters are supported:
legion@Virginia.edu
|