| Scyld ClusterWare HPC: Reference Guide | ||
|---|---|---|
| << Previous | Next >> | |
beosetup [-?, --help] [--usage] [--version]
[-d, --debug] [-c, --conf=CONFIGURATION_FILENAME]
[-n, --new=NEW_NODE_FILENAME] [-m, --cm=CLUSTER_MANAGER]
[--disable-sound] [--enable-sound] [--espeaker=HOST:PORT]
[--display=DISPLAY] [--sync] [--no-xshm]
[--gdk-debug=FLAGS] [--gdk-no-debug=FLAGS]
[--gtk-debug=FLAGS] [--gtk-no-debug=FLAGS]
[--gtk-module=MODULE]
[--name=NAME] [--class=CLASS]
[--gxid_host=HOST] [--gxid_port=PORT]
[--xim-preedit=STYLE] [--xim-status=STYLE]
[--g-fatal-warnings] [--disable-crash-dialog]
[--sm-client-id=ID] [--sm-config-prefix=PREFIX]
[--sm-disable]
The beosetup cluster configuration tool is a graphical tool for simplifying installation and control of the compute nodes in the cluster. Running beosetup isn't required for adding compute nodes; they will join the cluster by default. However, running beosetup as you initially power on the compute nodes gives you a graphical view of the nodes as they join the cluster.
beosetup is a thin layer over the underlying cluster functionality, not the cluster interface itself. Every operation that beosetup performs and every status that it reports is available from the command line, using scripts and with a library interface. Most of the configuration settings are written to the configuration file /etc/beowulf/config. Many of the actions, such as generating a boot floppy, report the command and options used to accomplish the task.
beosetup may be run by any user to monitor cluster node state, run commands, and read node logs; however, the full functionality is available only to the "root" user. When you start this tool as a user other than "root", you are asked for the root password. If you don't supply it, functionality is limited. For this reason, Scyld recommends running beosetup as "root".
The default display is a GTK X11 graphical display, and various other formats are available.
See the Installation Guide for additional information on beosetup.
The following options are available to the beosetup program.
General options:
Show this help message
Display brief usage message
Display version information
Enable internal state status messages
Configuration file read in initially and used for output continuously
New Node file read continuously for new nodes
Cluster Management type
X display to use
Make X calls synchronous
Don't use X shared memory extension
GTK options:
Gdk debugging flags to set
Gdk debugging flags to unset
Gtk+ debugging flags to set
Gtk+ debugging flags to unset
Load an additional Gtk module
Program name as used by the window manager
Program class as used by the window manager
Make all warnings fatal
Session management options:
Specify session management ID
Specify prefix of saved configuration
Disable connection to session manager
Run beosetup with default options to view the current cluster configuration and potentially modify the configuration:
[user@cluster user] $ beosetup |
The Config Boot option modifies the configuration of the selected (i.e., highlighted) nodes in the main window. If you want to modify the configuration for all nodes, then either select all nodes or no nodes.
If you use beosetup to manually insert a node prior to starting the cluster, then when the first compute node subsequently boots and auto-appends, that node thus becomes the next numbered node. If you then select the first node (which you just manually inserted) and delete it, then both the manually inserted node and the auto-appended node will be deleted.
Edits to the Display and Notes preferences do not persist between sessions. Only State Colors persist.
The log viewer accessed through the View Syslog option may not display the full output of the /var/log/messages file.
| << Previous | Home | Next >> |
| beorun | Up | beosi |