Define the dynamic external resources in lsf.shared. By default, these resources are host-based (local to each host) until the LSF administrator configures a resource-to-host-mapping in the ResourceMap section of lsf.cluster.cluster_name. The presence of the dynamic external resource in lsf.shared and lsf.cluster.cluster_name triggers LSF to start the elim executables.
Create one or more elim executables in the directory specified by the parameter LSF_SERVERDIR. LSF does not include a default elim; you should write your own executable to meet the requirements of your site. The section Create an elim executable provides guidelines for writing an elim.
Once external resources are defined in lsf.shared, they must be mapped to hosts in the ResourceMap section of lsf.cluster.cluster_name.
You can write one or more elim executables. The load index names defined in your elim executables must be the same as the external resource names defined in the lsf.shared configuration file.
3 tmp2 47.5 nio 344.0 licenses 5
The load update string must report values between -INFINIT_LOAD and INFINIT_LOAD as defined in the lsf.h header file.
If the elim executable is implemented as a C program, use setbuf(3) during initialization to send unbuffered output to stdout.
Each LIM sends updated load information to the master LIM every 15 seconds; the elim executable should write the load update string at most once every 15 seconds. If the external load index values rarely change, program the elim to report the new values only when a change is detected.
If you map any external resource as default in lsf.cluster.cluster_name, all elim executables in LSF_SERVERDIR run on all hosts in the cluster. If LSF_SERVERDIR contains more than one elim executable, you should include a header that checks whether the elim is programmed to report values for the resources expected on the host. For detailed information about using a checking header, see the section How environment variables determine elim hosts.
An elim executable can be used to override the value of a built-in load index. For example, if your site stores temporary files in the /usr/tmp directory, you might want to monitor the amount of space available in that directory. An elim can report the space available in the /usr/tmp directory as the value for the tmp built-in load index. However, the value reported by an elim must less than the maximum size of /usr/tmp.
Write an elim executable that periodically measures the value of the dynamic external resource and writes the numeric value to standard output. The external load index must correspond to a numeric, dynamic external resource as defined by TYPE and INTERVAL in lsf.shared.
Configure an external resource in lsf.shared and map the resource in lsf.cluster.cluster_name, even though you are overriding a built-in load index. Use a name other than the built-in load index, for example, mytmp rather than tmp.
Program your elim to output the formal name of the built-in index (for example, r1m, it, ls, or swp), not the resource name alias (cpu, idle, login, or swap). For example, an elim that collects the value of the external resource mytmp reports the value as tmp (the built-in load index) in the load update string: 1 tmp 20.
The file elim.jsdl is automatically configured to collect these resources. To enable the use of elim.jsdl, uncomment the lines for these resources in the ResourceMap section of the file lsf.cluster.cluster_name.
See the section How environment variables determine elim hosts for an example of a simple elim script.
You can find additional elim examples in the LSF_MISC/examples directory. The elim.c file is an elim written in C. You can modify this example to collect the external load indices required at your site.