Installation guide

Release Notes
If that reconfiguration is also not possible, you may need to increase the default Scyld ClusterWare timeout used
by the node to a value safely greater than the STP delay: e.g., add rootfs_timeout=120 getfile_timeout=120 to the
/etc/beowulf/config kernelcommandline entry to increase the timeouts to 120 seconds.
Issues with Gdk
If you access a cluster master node using ssh -X from a workstation, some graphical commands or program may fail with:
Gdk-ERROR **: BadMatch (invalid parameter attributes)
serial 798 error_code 8 request_code 72 minor_code 0
Gdk-ERROR **: BadMatch (invalid parameter attributes)
serial 802 error_code 8 request_code 72 minor_code 0
Remedy this by doing:
export XLIB_SKIP_ARGB_VISUALS=1
prior to running the failing program. If this workaround is successful, then consider adding this line to /etc/bashrc or to
~/.bashrc. See https://bugs.launchpad.net/ubuntu/+source/xmms/+bug/58192 for details.
Caution when modifying Scyld ClusterWare scripts
Scyld ClusterWare installs various scripts in /etc/beowulf/init.d/ that node_up executes when booting each node in
the cluster. Any site-local modification to one of these scripts will be lost when a subsequent Scyld ClusterWare update
overwrites the file with a newer version. If a cluster administrator believes a local modification is necessary, we suggest:
1. Copy the to-be-edited original script to a file with a unique name, e.g.:
cd /etc/beowulf/init.d
cp 20ipmi 20ipmi_local
2. Remove the executable state of the original:
/sbin/beochkconfig 20ipmi off
3. Edit 20ipmi_local as desired.
4. Thereafter, subsequent Scyld ClusterWare updates may install a new 20ipmi, but that update will not re-enable the
non-executable state of that script. The locally modified 20ipmi_local remains untouched. However, keep in mind
that the newer Scyld ClusterWare version of 20ipmi may contain fixes or other changes that need to be reflected in
20ipmi_local because that edited file was based upon an older Scyld ClusterWare version.
Caution using tools that modify config files touched by Scyld ClusterWare
Software tools exist that might make modifications to various system configuration files that Scyld ClusterWare also modi-
fies. These tools do not have knowledge of the Scyld ClusterWare specific changes and therefore may undo or cause damage
to the changes or configuration. Care must be taken when using such tools. One such example is /usr/sbin/authconfig,
which manipulates /etc/nsswitch.conf.
Scyld ClusterWare modifies these system configuration files at install time:
/etc/exports
/etc/nsswitch.conf
22