| Scyld ClusterWare HPC: Administrator's Guide | ||
|---|---|---|
| << Previous | Special Directories, Configuration Files, and Scripts | |
Local, homegrown scripts to be executed at node boot time can be placed in /etc/init.d/. The conventions for this are as follows:
Scripts should live in /etc/init.d/
Scripts should be numbered in the order in which they are to be executed (e.g., 20raid, 30startsan, 45mycustom_hw)
Any scripts going into /etc/beowulf/init.d/ should be cluster aware. That is, they should contain the appropriate bpsh and/or bpcp commands to make the script work on the compute node rather than on the master node. Examine the Scyld ClusterWare-distributed scripts for examples.
Any local modifications to Scyld ClusterWare-distributed scripts in /etc/beowulf/init.d will be lost across subsequent Scyld ClusterWare updates. If a local sysadmin believes a local modification is necessary, we suggest:
Copy the to-be-edited original script to a file with a unique name, e.g.:
cd /etc/beowulf/init.d
cp 37some_script 37some_script_local |
Remove the executable state of the original:
beochkconfig 37some_script off |
Edit 37some_script_local as desired.
Thereafter, subsequent ClusterWare updates may install a new 37some_script, but the update will not re-enable the non-executable state of that script. The local 37some_script_local remains untouched. However, keep in mind that the newer ClusterWare version of 37some_script may contain fixes or other changes that need to be reflected in 37some_script_local because that edited file was based upon an older ClusterWare version.
| << Previous | Home | |
| What Gets Put on the Compute Nodes at Boot Time | Up |