Using and Administering

llinit - Initialize Machines in the LoadLeveler Cluster

Purpose

Initializes a new machine as a member of the LoadLeveler hardware resource cluster

Syntax

llinit [-?] [-H] [-q] [-prompt] [-local pathname] [-release pathname] [-cm machine] [-debug]

Flags

-?
Provides a short usage message.

-H
Provides extended help information.

-q
Specifies quiet mode: print no messages other than error messages.

-prompt
Prompts or leads you through a set of questions that help you to complete the llinit command.

-local pathname
Where pathname is the local directory on which to create the spool, execute, and log sub-directories. The default, if this flag is not used, is the home directory.

There must be a unique local directory for each LoadLeveler cluster member.

-release pathname
Where pathname is the release directory, where the LoadLeveler bin, lib, man, include, and samples subdirectories are located. The default, if this flag is not used, is the /usr/lpp/LoadL/full directory.

-cm machine
Where machine is the central manager machine, where the negotiator daemon runs.

-debug
Displays a large amount of messages, tracing the path through llinit during execution. This is intended for debugging purposes only.

Description

This command runs once on each machine during the installation process. It must be run by the user ID you have defined as the LoadLeveler user ID. The log, spool, and execute directories are created with the correct modes and ownerships. The LoadLeveler configuration and administration files, LoadL_config and LoadL_admin, respectively, are copied from LoadLeveler's release directory to LoadLeveler's home directory. The local configuration file, LoadL_config.local, is copied from LoadLeveler's release directory to LoadLeveler's local directory.

llinit initializes a new machine as a member of the LoadLeveler resource cluster by doing the following:

Before running llinit ensure that your HOME environment variable is set to LoadLeveler's home directory. To run llinit you must have:

Examples

The following example initializes a machine, assigning /var/loadl as the local directory, /usr/lpp/LoadL/full as the release directory, and the machine named bronze as the central manager.

llinit -local /var/loadl -release /usr/lpp/LoadL/full -cm bronze

Results

The command:

llinit -local /home/ll_admin -release /usr/lpp/LoadL/full -cm mars

will yield the following output:

llinit: creating directory "/home/ll_admin/spool"
llinit: creating directory "/home/ll_admin/log"
llinit: creating directory "/home/ll_admin/execute"
llinit: set permission "700" on "/home/ll_admin/spool"
llinit: set permission "775" on "/home/ll_admin/log"
llinit: set permission "1777" on "/home/ll_admin/execute"
llinit: creating file "/home/ll_admin/LoadL_admin"
llinit: creating file "/home/ll_admin/LoadL_config"
llinit: creating file "/home/ll_admin/LoadL_config.local"
llinit: editing file /home/ll_admin/LoadL_config
llinit: editing file /home/ll_admin/LoadL_admin
llinit: creating symbolic link "/home/ll_admin/bin -> /usr/lpp/LoadL/full/bin"
llinit: creating symbolic link "/home/ll_admin/lib -> /usr/lpp/LoadL/full/lib"
llinit: creating symbolic link "/home/ll_admin/man -> /usr/lpp/LoadL/full/man"
llinit: creating symbolic link "/home/ll_admin/samples -> /usr/lpp/LoadL/full/samples"
llinit: creating symbolic link "/home/ll_admin/include -> /usr/lpp/LoadL/full/include"
llinit: program complete.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]