Supporting the contention that a significant amount of useful Grid Engine admin/usage information is often found outside of the formal documentation:
I learned two new things today while working on a load sensor project. The information was recently discussed on the mailing list and is hidden in plain view within the manpage but you certainly will not see it mentioned in the official documentation.
- The load_sensor parameter can accept a comma-separated list of script(s). Assuming SGE would only accept a single script path for that parameter I’ve often written load sensor scripts that called multiple other scripts.
- If you drop an executable program named qloadsensor into the SGE binary path on an execution host, it will be run as a load sensor!
The relevant excerpts from the sge_conf manpage are here:
A comma separated list of executable shell script paths or programs to be started by sge_execd(8) and to be used in order to retrieve site configurable load information (e.g. free space on a certain disk partition) …
… In addition to the load sensors configured via load_sensor, sge_exec(8) searches
for an executable file named qloadsensor in the execution host’s Grid Engine binary
directory path. If such a file is found, it is treated like the configurable load
sensors defined in load_sensor. This facility is intended for pre-installing a
default load sensor.