The full procedure explained below can be used for adding new host or vault objects with the command-line procedure to a system spanning multiple file systems or to a Legion system with a common file system. For a system spanning multiple file systems, however, skip steps 2 and 3. In either case, the main Legion system must be active. Start it with the first-time start-up or restart procedure, if necessary.
Once an extra host or vault has been safely shut down, it can be restarted. If the host or vault was not safely shut down, you cannot restart it, but must delete the OPR directory, restart Legion, and start the host or vault again (see "System restart," pg. 24, in the System Administrator Manual).
Generally, you can use a single host to start a new Legion system, but if your machines are strapped for memory you may need to split the process between two hosts. Technically, you can use two hosts used for the whole procedure, the start-up host and the bootstrap host (Figure 1): start Legion from one host and use a different host as the bootstrap.
The start-up host must always be used to run legion_startup. The host that you select during legion_setup_state and that contains the basic Legion classes is the start-up host. The bootstrap host is used to boot the system and is the first host object added to the system. It will contain the first pieces of the new system (the first contexts and instances of the classes). In either case, Legion binary executable files must be installed on any hosts used for Legion procedures. That is, you don't have to run legion_startup in order to use the host in a Legion net: you just have to have the binary files. You do not have to run legion_initialize on the same host on which you run legion_setup_state and legion_startup.
1. If preferred, ssh can be used in place of rsh. Back