If you are very familiar with UNIX system administration and job scheduling, follow the steps listed in this section to get LoadLeveler up and running on your network quickly in a default configuration. This default configuration will merely enable you to submit serial jobs; for a more complex setup, you will have to consult the rest of this manual. This section also does not address how to configure DCE. For more information about configuring DCE for LoadLeveler, see Step 16: Configuring LoadLeveler to use DCE Security Services. For this set up, it is recommended that you use loadl as the LoadLeveler user ID. Afterward, you can fine tune your configuration for greater efficiency when you become more familiar with the details of LoadLeveler.
Refer to Step 1: Define LoadLeveler Administrators for more information.
machinename: type = machine central_manager = true
Do not specify more than one machine as the central manager. Also, if during installation, you ran llinit with the -cm flag, the central manager is already defined in the LoadL_admin file because the llinit command takes parameters you entered and updates the administration and configuration files. See Step 1: Specify Machine Stanzas for more information.
llctl -h hostname start
Issue this command for the central manager machine first. See llctl - Control LoadLeveler Daemons for more information.
You can also issue the following command to start LoadLeveler on all machines beginning with the central manager. Before you issue this command, make sure all the machines are listed in the administration file. This command only affects machines that are defined in the administration file.
llctl -g start
llctl uses rsh or remsh to start LoadLeveler on the target machine. Therefore, the administrator using llctl must have rsh authority on the target machine.