Filter
Top Products
Setting up RMS
for this command to work correctly. This should have been enabled as part of the
installation.
# rmsctl start
Configure all of the nodes into the machine using rcontrol.
# rcontrol configure in ’atlas[0-63]’
Use rinfo with the -n option to check the status of the nodes. The output should show
that all of the nodes are running.
# rinfo -n
running atlas[0-63], atlasms
If any of the nodes show a status other than running, restart them by running
/sbin/init.d/rms on the nodes in question. For example, to restart RMS on atlas3,
enter the following:
# /sbin/init.d/rms stop
# /sbin/init.d/rms start
If necessary, configure out any nodes that fail:
# rcontrol configure out atlas3
Restarting RMS
RMS daemons such as the Machine Manager and the Partition Manager can be stopped
and started by executing the /sbin/init.d/rms script on the rmshost node. When
run on the rmshost node, the init script checks the status of each of the partitions in the
active configuration. If a partition is in the running state or blocked state, the
partition is stopped and its autostart field in the servers table is set to 1, otherwise
the field is set to 0. When the node boots, only those partitions that have their
autostart field set to 1, are restarted. This means that the state of the configuration is
preserved.
By contrast, if rmsctl is used to start and stop the machine, all of the partitions in the
active configuration are started: when rmsctl stops RMS, it sets all of the autostart
fields to 0; when it starts RMS, it sets them to 1.
9.3.2 Initial Setup with One Partition
This example describes the simplest possible setup. All nodes are in a single partition
and there are no memory limits, time limits or access controls. Any user can run a job
using all of the CPUs.
Setting up RMS 9-3