Appendices

A-1.0 About Legion tty objects

A Legion tty object directs output from Legion processes towards a specific shell. This means that you can see the output from a remotely executed program on your workstation, direct output from a locally executed program into a file, or perhaps view the output from several simultaneously executed programs in a single shell. Generally, you will want one tty object per shell, so that each shell's output will appear in that shell, regardless of where its processes are run.

There are three steps involved in using Legion tty objects:

  1. Create an instance of the ttyObjectClass.
  2. Set a tty object for the shell. This means that all output resulting from processes run in the shell will be directed towards the set tty object. Only one tty object can be set per shell.
  3. Watch the output that arrives at a tty object. This involves creating a special tty watch object, which runs a tty_watch process. This process constantly watches its assigned tty object and sends a copy of any input the tty object receives to standard output in its shell. Note that a shell does not have to watch its set tty object, and that multiple shells can watch the same tty object.

Note that when you exit from a shell the tty_watch process will not automatically shut down. That is, it will continue to send information to the now defunct shell. This will bog down the tty process and may result in error messages. We therefore suggest that before you exit a shell you stop the tty_watch process.

There are two different ways to create and use tty objects in Legion, a simple approach, which will probably be acceptable for most users, and a complex approach.

A-1.1 Simple tty management

There are two commands for the simple approach: legion_tty and legion_tty_off. The former creates, sets, and watches a tty object and the latter stops the tty_watch process, so that the output from the shell will no longer be directed towards the shell. Usage for legion_tty is:

$ legion_tty <context path>

You might find it convenient to create a specific context (e.g., /tty_objects) to hold your tty objects.

$ legion_tty /tty_objects/mytty

If mytty does not already exist, a new tty object will be created and assigned the context path name /tty_objects/mytty. The output from all processes run in your current shell, whether on your local system or a foreign system, will now be directed to mytty, and a tty_watch process will start. This process will watch its assigned tty object and pass a copy of the tty object's information to the shell's standard output (i.e., to the shell's command line). Note that a shell can run only one tty_watch process at a time.

To stop the tty_watch process, run the legion_tty_off command. This will end whatever tty_watch process is currently running in the current shell, although it will not destroy the tty object being watched.

A-1.2 Complex tty management

The complex procedure requires three different commands to create, set, and watch the tty object.

First, if you do not already have a tty object you must use legion_create_object to create a tty object. Then use legion_set_tty to set a tty object for your shell. Remember that you can only have one tty object set per shell. If a tty object has already been set, legion_set_tty will just switch to the new one. Finally, use legion_tty_watch to start watching your current (set) tty object. The whole procedure looks something like this:

$ legion_create_object -c /class/ttyObjectClass \
   /context_path/mytty
$ legion_set_tty /tty_objects/mytty
$ legion_tty_watch &

The legion_tty_watch command can be run with or without a tty object's name: multiple tty_watches can be run, and can be started at different times. They can be piped to a file, or run in a different window, as desired. To stop the tty_watch procedure, send a SIGINIT, using either "kill -INT" or the Ctrl-C key combination.

To direct the current tty object's output to a file object instead of standard output, use the legion_tty_redirect command. The example below redirects the current tty's object output to file object Foo. If no file object of that name exists, Legion will create a new one.

$ legion_tty_redirect Foo

Use legion_tty_unredirect to stop this process.

A-2.0 Alphabetical list of Legion commands

Full documentation of these commands can be found in the Reference Manual, in Command-line functions. There are also man pages for all Legion commands included in the system release package, and on-line tutorials on the Legion web site (<http://legion.virginia.edu>).

legion_activate_instances 
{-l <class LOID> | -c <class context path>}
legion_activate_object 
{-l <object LOID> | -c <context path>}
legion_add_implicit_params 
[-l <AuthenticationObject LOID> | -c <AuthenticationObject context path>]
{-s | <filename>}
legion_add_class_mapping 
<metaclass LOID> <class LOID>
legion_bfs 
<file> [-o <out file>] [-BackEnd]
legion_cat 
<context path>
legion_change_owner 
[-h] [-v] [-r] 
{-l <object LOID> | -c <object context path>}
{-l <target owner LOID> | -c <target owner context path>}
legion_change_permissions 
[+-rwx] [-v] [-help] 
<group/user context path> <target context path>
legion_check_system 
[-help] [-v] [-q]
legion_class_host_list 
[-l <class LOID> | -c <class context path>]
[{-a | -d | -t} <host1> <host2> ... <hostn>] 
[-p] [-u]
legion_class_vault_list 
[-l <class LOID> | -c <class context path>}
[{-a | -d | -t} <vault1> <vault2> ... <vaultn>] 
[-p] [-u]
legion_classof 
{-l <object LOID> | -c <context path>}
legion_combine_domains 
[-help] [-v] 
[-C <target domain context path>]
<OPR directory for target domain>
legion_config_scheduler 
{-l <scheduler LOID> | -c <scheduler context path>} 
[-get_enactor] [-get_collection] 
[-set_enactor {-l <Enactor LOID> | -c <Enactor path>}] 
[-set_collection {-l <Collection LOID> | -c <Collection path>}]
legion_context_add 
<object LOID> <context name>
legion_context_create 
<context path>
legion_cp 
[-help][-r][-v][-m][-p]
[-localsrc][-localdest]
[-V <vault context path>] 
<source path> <destination path>
legion_create_class 
[-help] 
[-c <context path>] 
[-sc <scheduler context path>] 
[-sl <scheduler LOID>]
legion_create_implementation 
<binary path name> <architecture>
{-l <class LOID> | -c <context path>}
legion_create_object
{-l <class LOID> | -c <class context path>}
<new object context path>
[-h <host name on which to place new object>]
[-v <vault on which to place new object>]
[-H <context path of preferred host class>]
[-V <context path of preferred vault class>]
[-Ch <context containing list of preferred hosts>]
[-Cv <context containing list of preferred vaults>]
legion_create_object_r 
{-l <class LOID> | -c <class context path>} 
<context path> <host name> <host architecture> 
<$LEGION> <$LEGION_OPR> <$LEGION_OPA> 
<binary path> [<user id>]
legion_create_stat_tree 
<base context path>
legion_create_user 
<user id>
legion_deactivate_instances 
{-l <class LOID> | -c <class context path>}
legion_deactivate_object 
{-l <object LOID> | -c <context path>}
legion_destroy_instances 
{-l <class LOID> | -c <class context path>}
legion_destroy_host [-help] [-v] 
{-l <host LOID> | -c <host context path>}
legion_destroy_object 
{-l <object LOID> | -c <context path>}
legion_destroy_vault 
{-l <vault LOID> | -c <vault context path>}
legion_direct_output 
{-l <object LOID> | -c <object path>}
{-l <tty LOID> | -c <tty context path>}
legion_exports_interface 
{-l <LOID> | -c <context path>}
{-w <well-known class type> | -f <function signature>}+
legion_generate_idl 
[<flags>] <input file local path>
legion_get_acl 
{-l <LOID> | -c <context>}
legion_get_candidate_hosts
{-l <object LOID> | -c <object context path>}
legion_get_candidate_placements 
{-l <class LOID> <instance LOID>} | {-c <class context path> <instance context path>} [<max placements>]
legion_get_candidate_vaults 
{-l <object LOID> | -c <object context path>}
legion_get_host 
{-l <object LOID> | -c <object context path>}
legion_get_implicit_params 
[-l <LOID> | -c <context path>]
legion_get_interface 
{-l <class LOID> | -c <context path>}
legion_get_vault 
{-l <object LOID> | -c <object context path>}
legion_host_stats 
{-l <host LOID> | -c <host context path>}
legion_host_vault_list 
{-l <host LOID> | -c <host context path>]
[{-a | -d | -t} <vault1> <vault2> ... <vaultn>] 
[-p] [-u]
legion_import_tree 
[<unix directory path> [<legion context path>]]
legion_init_arch
legion_init_security
legion_initialize
legion_instance_host_list 
{-l <LOID> | -c <context path>}
[{-a | -d | -t} <host1> <host2> ... <hostn>] 
[-p] [-u]
legion_java <java options>
legion_join_collection 
{-l <Collection LOID> | -c <Collection path>}
{-l <member LOID> | -c <member path>}
legion_leave_collection 
{-l <Collection LOID> | -c <Collection path>}
{-l <member LOID> | -c <member path>}
legion_link 
[-CC <compiler>] [-Fortran] [-pvm] [-mpi] 
[-L<library path>] [-l<library>] 
[-v] [-o <output file>] 
[-bfs] [-help] <object file list>
legion_list_attributes 
{-l <object LOID> | -c <context path>} 
[-L] [<attribute name>]
legion_list_domains
legion_list_implementations 
[-v] {-l <class LOID> | -c <class context path>}
legion_list_instances 
{-l <class LOID> | -c <context path>}
legion_list_invocations 
{-l <object LOID> | -c <object context path>}
legion_list_names 
{-l <object LOID> | -c <object context path>}
legion_list_objects 
{-l <host LOID> | -c <host context path>}
legion_list_oprs 
{-l <vault LOID> | -c <vault context path>}
legion_ln 
<context path> <new alias>
legion_login 
[-l <user LOID> | <user id>] [-e <command>]
legion_login
-x [-e <command>]
legion_ls 
[-laLAdqvh] <context path>
legion_make 
[-help] [-v] 
[-a <architecture>] [-h <host context path>]
[-e <make command>] [-OUT <remote file>] 
[<arg1> <arg2> ... <argn>]
legion_make_idl 
[-notrans] [-noclient] [-v] [-noreg]
[-s <suffix string>] [-run] [-help] 
<application name>
legion_make_multi 
[-help] [-v] 
[-a <architecture>][-e <make command>]
[<arg1> <arg2> ... <argn>]
legion_make_setup_script 
[-help] [-o <script basename>]
[-OPR <OPR dir name>] 
[-L <$LEGION dir name>]
legion_mplc
legion_mplc_reg_impl
<class name> <binary path> 
<stateless | stateful | sequential> 
<arch>
legion_mpi_debug 
[-q] {-c <instance context path>}
legion_mpi_register 
<class name> <binary local path name> <platform type>
legion_mpi_run 
{-f <options file> [<flags>]} | {-n <number of hosts> [<flags>] 
<command> [<arguments>]}
legion_mv 
<context path> <new context path>
legion_object_info 
[-l <object LOID> | -c <object context path>]
legion_passwd 
{-l <user LOID> | <user id>}
legion_ping 
{-l <object LOID> | -c <context path>}
legion_print_config
legion_pvm_register 
<class path name> <binary local path name> <platform type>
legion_pwd
legion_query_collection 
[-v] 
{-l <Collection LOID> | -c <Collection path>} 
<query>
legion_register_program 
<program class> <executable path> <legion arch>
legion_register_runnable 
<program class> <executable path> <legion arch>
legion_rm 
[-r] [-f] [-v] <context path list>
legion_run 
[-help] [-w] [-v]
[-a <architecture>]
[-h <host context path name>]
[-in <context path name>] [-out <context path name>] 
[-IN <local file name>] [-OUT <local file name>]
[-f <options file>] <program class> 
[-t <minutes>] [-n <nodes>]
[<arg1> <arg2> ... <argn>]
legion_run_multi 
[-v] {-n <number of processors>}
[-s <schedule file name>]
{-f <specification file name>}
<program class name>
[<arg1> <arg2> ... <argn>]
legion_set_acl 
{-l <object LOID> | -c <object context path>}
[-s | filename]
legion_set_context 
<context path>
legion_set_default_placement 
{-l <class LOID> | -c <class context name>}
{-l <host LOID> | -c <host context name>}
{-l <vault LOID> | -c <vault context name>}
legion_set_host 
{-l <object LOID> | -c <object context path} 
{-l <host LOID> | -c <host context path>}
legion_set_implicit_params 
[-l <object LOID> | -c <object context path>]
[-s | filename]
legion_set_scheduler 
{-l <class LOID> | -c <class context path>}
{-l <Scheduler LOID> | -c <Scheduler context path>}
legion_set_scheduler_policy 
{-l <class LOID> | -c <class context path>} <policy>
legion_set_tty 
<tty context path>
legion_set_vault 
{-l <object LOID> | -c <object context path} 
{-l <vault LOID> | -c <vault context path>}
legion_setup_state 
[-i]
legion_shutdown 
[-local] [-f] [-i] [-h]
legion_shutdown_class 
{-l <class LOID> | -c <context path>}
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>]
legion_startup 
[-local]
legion_startvault 
[-L <$LEGION>] [-O <$LEGION_OPR>] [-A <$LEGION_ARCH>] 
[-N <context name>] [-U <user id>] 
{<host name>} 
[<compatible host list>]
legion_stateless_add_workers 
<class name>
<worker name1> <worker name2> ... <worker nameN>
legion_stateless_configure 
<stateless class context path> 
[-n <number of replicas>] 
[-Ch <host conte1xt path>]
[-w <max number work requests>] 
[-FlUsH]
legion_stateless_remove_workers 
<class name>
<worker name1> <worker name2> ... <worker nameN>
legion_tty 
<tty context path>
legion_tty_off
legion_tty_redirect 
<object context path>
legion_tty_unredirect 
<object context path>
legion_tty_watch 
[-l <tty LOID> | -c <tty context path>]
legion_update_attributes 
{-l <object LOID> | -c <context path>}
[{-a | -d | -t} <attribute description>] 
[-u]
legion_vault_host_list 
{-l <vault LOID> | -c <vault context path>}
[{-a | -d | -t} <host1> <host2> ... <hostn>] 
[-p] [-u]
legion_version
legion_wellknown_class 
<well-known class name>
legion_whereis 
{-l <object LOID> | -c <object context path>}
legion_whoami

A-3.0 Subject listing of Legion commands

Full documentation of these commands can be found in the Reference Manual, in Command-line functions, and on the Legion web site at <http://legion.virginia.edu/documentation/tutorials/1.5/tutorials_1.5.html>. There are also man pages for all Legion commands included in the system release package.

A-3.1 Calls on Objects

legion_exports_interface 
{-l <LOID> | -c <context path>}
{-w <well-known class type> | -f <function signature>}+
legion_get_interface 
{-l <class LOID> | -c <context path>}
legion_ping 
{-l <object LOID> | -c <context path>}
legion_list_attributes 
{-l <object LOID> | -c <context path>} 
[-L] [<attribute name>]
legion_list_invocations 
{-l <object LOID> | -c <object context path>}
legion_object_info 
[-l <object LOID> | -c <object context path>]
legion_update_attributes 
{-l <object LOID> | -c <context path>}
[{-a | -d | -t} <attribute description>] 
[-u]

A-3.2 Calls on Class Objects

legion_activate_object 
{-l <object LOID> | -c <context path>}
legion_create_object 
{-l <class LOID> | -c <class context path>}
<new object context path>
[-h <host name on which to place new object>]
[-v <vault on which to place new object>]
[-H <context path of preferred host class>]
[-V <context path of preferred vault class>]
[-Ch <context containing list of preferred hosts>]
[-Cv <context containing list of preferred vaults>]
legion_create_object_r 
{-l <class LOID> | -c <class context path>} 
<context path> <host name> <host architecture> 
<$LEGION> <$LEGION_OPR> <$LEGION_OPA> 
<binary path> [<user id>]
legion_deactivate_object 
{-l <object LOID> | -c <context path>}
legion_destroy_object 
{-l <object LOID> | -c <context path>}
legion_get_host 
{-l <object LOID> | -c <object context path>}
legion_get_vault 
{-l <object LOID> | -c <object context path>}
legion_list_implementations 
[-v] {-l <class LOID> | -c <class context path>}
legion_list_instances 
{-l <class LOID> | -c <context path>}
legion_set_host 
{-l <object LOID> | -c <object context path} 
{-l <host LOID> | -c <host context path>}
legion_set_vault 
{-l <object LOID> | -c <object context path} 
{-l <vault LOID> | -c <vault context path>}

A-3.3 Calls on LegionClass

legion_add_class_mapping 
<metaclass LOID> <class LOID>
legion_combine_domains 
[-help] [-v] 
[-C <target domain context path>]
<OPR directory for target domain>
legion_create_implementation 
<binary path name> <architecture>
{-l <class LOID> | -c <context path>}
legion_init_arch
legion_list_domains

A-3.4 Calls on File and Context Objects

legion_activate_instances 
{-l <class LOID> | -c <class context path>}
legion_cat 
<context path>
legion_context_add 
<object LOID> <context name>
legion_context_create 
<context path>
legion_cp 
[-help][-r][-v][-m][-p]
[-localsrc][-localdest]
[-V <vault context path>] 
<source path> <destination path>
legion_deactivate_instances 
{-l <class LOID> | -c <class context path>}
legion_destroy_instances 
{-l <class LOID> | -c <class context path>}
legion_direct_output 
{-l <object LOID> | -c <object path>}
{-l <tty LOID> | -c <tty context path>}
legion_get_host 
{-l <object LOID> | -c <object context path>}
legion_get_vault 
{-l <object LOID> | -c <object context path>}
legion_import_tree 
[<unix directory path> [<legion context path>]]
legion_list_names 
{-l <object LOID> | -c <object context path>}
legion_ln 
<context path> <new alias>
legion_ls 
[-laLAdqvh] <context path>
legion_mv 
<context path> <new context path>
legion_pwd
legion_rm 
[-r] [-f] [-v] <context path list>
legion_set_context 
<context path>
legion_set_tty 
<tty context path>
legion_tty 
<tty context path>
legion_tty_off
legion_tty_redirect 
<object context path>
legion_tty_unredirect 
<object context path>
legion_tty_watch 
[-l <tty LOID> | -c <tty context path>]

A-3.5 Start-Up and Shutdown Functions

legion_create_class 
[-help] [-c <context path>] 
[-sc <scheduler context path>] [-sl <scheduler LOID>]
legion_destroy_host 
[-help] [-v] 
{-l <host LOID> | -c <host context path>}
legion_destroy_vault 
{-l <vault LOID> | -c <vault context path>}
legion_initialize
legion_make_setup_script 
[-help] [-o <script basename>]
[-OPR <OPR dir name>] [-L <$LEGION dir name>]
legion_print_config
legion_setup_state 
[-i]
legion_shutdown 
[-local] [-f] [-i] [-h]
legion_shutdown_class 
{-l <class LOID> | -c <context path>}
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>]
legion_startup 
[-local]
legion_startvault 
[-L <$LEGION>] [-O <$LEGION_OPR>] [-A <$LEGION_ARCH>] 
[-N <context name>] [-U <user id>] 
{<host name>} [<compatible host list>]

A-3.6 Scheduling Support

legion_class_host_list 
[-l <class LOID> | -c <class context path>]
[{-a | -d | -t} <host1> <host2> ... <hostn>] 
[-p] [-u]
legion_class_vault_list 
[-l {<class LOID> | -c <class context path>}
[{-a | -d | -t} <vault1> <vault2> ... <vaultn>] 
[-p] [-u]
legion_config_scheduler 
{-l <scheduler LOID> | -c <scheduler context path>} 
[-get_enactor] [-get_collection] 
[-set_enactor {-l <Enactor LOID> | -c <Enactor path>}] 
[-set_collection {-l <Collection LOID> | -c <Collection path>}]
legion_get_candidate_hosts 
{-l <object LOID> | -c <object context path>}
legion_get_candidate_placements 
{-l <class LOID> <instance LOID>} | {-c <class context path> <instance context path>} [<max placements>]
legion_get_candidate_vaults 
{-l <object LOID> | -c <object context path>}
legion_host_vault_list 
{-l <host LOID> | -c <host context path>]
[{-a | -d | -t} <vault1> <vault2> ... <vaultn>] 
[-p] [-u]
legion_instance_host_list 
{-l <LOID> | -c <context path>}
[{-a | -d | -t} <host1> <host2> ... <hostn>] 
[-p] [-u]
legion_join_collection 
{-l <Collection LOID> | -c <Collection path>}
{-l <member LOID> | -c <member path>}
legion_leave_collection 
{-l <Collection LOID> | -c <Collection path>}
{-l <member LOID> | -c <member path>}
legion_list_oprs 
{-l <vault LOID> | -c <vault context path>}
legion_query_collection 
[-v] 
{-l <Collection LOID> | -c <Collection path>} 
<query>
legion_set_default_placement 
{-l <class LOID> | -c <class context name>}
{-l <host LOID> | -c <host context name>}
{-l <vault LOID> | -c <vault context name>}
legion_set_scheduler 
{-l <class LOID> | -c <class context path>}
{-l <Scheduler LOID> | -c <Scheduler context path>}
legion_set_scheduler_policy 
{-l <class LOID> | -c <class context path>} 
<policy>
legion_vault_host_list 
{-l <vault LOID> | -c <vault context path>}
[{-a | -d | -t} <host1> <host2> ... <hostn>] 
[-p] [-u]

A-3.7 General Functions About the State of the System

legion_check_system 
[-help] [-v] [-q]
legion_classof 
{-l <object LOID> | -c <context path>}
legion_create_stat_tree 
<base context path>
legion_host_stats 
{-l <host LOID> | -c <host context path>}
legion_list_objects 
{-l <host LOID> | -c <host context path>}
legion_version
legion_wellknown_class 
<well-known class name>
legion_whereis 
{-l <object LOID> | -c <object context path>}
legion_whoami

A-3.8 Security

legion_add_implicit_params 
[-l <AuthenticationObject LOID> | -c <AuthenticationObject context path>] {-s | <filename>}
legion_change_owner 
[-h] [-v] [-r] 
{-l <object LOID> | -c <object context path>}
{-l <target owner LOID> | -c <target owner context path>}
legion_change_permissions [+-rwx] [-v] [-help] 
<group/user context path> <target context path>
legion_create_user 
<user id>
legion_get_acl 
{-l <LOID> | -c <context>}
legion_get_implicit_params 
[-l <LOID> | -c <context>]
legion_init_security
legion_login 
[-l <user LOID> | <user id>] [-e <command>]
legion_login 
-x [-e <command>]
legion_passwd 
{-l <user LOID> | <user id>}
legion_set_acl 
{-l <object LOID> | -c <object context path>}
[-s | filename]
legion_set_implicit_params 
[-l <object LOID> | -c <object context path>]
[-s | filename]

A-3.9 Application Development

legion_bfs 
<file> [-o <out file>] 
[-BackEnd]
legion_generate_idl 
[<flags>] <input file local path>
legion_make 
[-help] [-v] 
[-a <architecture>] [-h <host context path>]
[-e <make command>] 
[-OUT <remote file>] 
[<arg1> <arg2> ... <argn>]
legion_make_idl 
[-notrans] [-noclient] [-v] [-noreg]
[-s <suffix string>] [-run] [-help] 
<application name>
legion_make_multi 
[-help] [-v] 
[-a <architecture>][-e <make command>]
[<arg1> <arg2> ... <argn>]
legion_mplc
legion_mplc_reg_impl 
<class name> <binary path> 
<stateless | stateful | sequential> 
<arch>
legion_java 
<java options>
legion_stateless_add_workers
<class name>
<worker name1> <worker name2> ... <worker nameN>
legion_stateless_configure 
<stateless class context path> 
[-n <number of replicas>] 
[-Ch <host context path>]
[-w <max number work requests>] 
[-FlUsH]
legion_stateless_remove_workers 
<class name>
<worker name1> <worker name2> ... <worker nameN>

A-3.10 Program Support

legion_run_multi 
[-v] {-n <number of processors>}
[-s <schedule file name>]
{-f <specification file name>}
<program class name> 
[<arg1> <arg2> ... <argn>]
legion_link 
[-CC <compiler>] [-Fortran] [-pvm] [-mpi] 
[-L<library path>] [-l<library>] 
[-v] [-o <output file>] 
[-bfs] [-help] 
<object file list>
legion_mpi_debug 
[-q] {-c <instance context path>}
legion_mpi_register 
<class name> <binary local path name> 
<platform type>
legion_mpi_run 
{-f <options file> [<flags>]} | 
{-n <number of hosts> [<flags>] <command> [<arguments>]}
legion_pvm_register 
<class path name> <binary local path name> <platform type>
legion_register_program 
<program class> <executable path> <legion arch>
legion_register_runnable 
<program class> <executable path> <legion arch>
legion_run 
[-help] [-w] [-v]
[-a <architecture>] [-h <host context path name>]
[-in <context path name>] [-out <context path name>] 
[-IN <local file name>] [-OUT <local file name>] 
[-f <options file>] <program class> 
[-t <minutes>] [-n <nodes>]
[<arg1> <arg2> ... <argn>]

Back to Basic User Manual Table of Contents

Directory of Legion 1.5 Manuals