LSF_STRICT_CHECKING
Syntax
LSF_STRICT_CHECKING=Y | N | ENHANCED
Description
If set to Y, enables more strict checking of communications between LSF daemons and between LSF commands and daemons when LSF is used in an untrusted environment, such as a public network like the Internet.
If set to ENHANCED, LSF also adds a checksum to each authorization request in addition to enabling more strict checking of communications between LSF daemons and between LSF commands and daemons. This ensures that any authorization request that is sent to LSF is identified if it is modified, which prevents users from changing either the user credential or the content of the LSF authentication requests.
If set to N, LSF does not have a checksum to each authorization requires and does not use strict checking of communications between LSF daemons and between LSF commands and daemons. Do not set to N unless LSF is fully secure in a trusted environment.
If you set this parameter, you must set it to the same value in the entire cluster, as it affects all communications within LSF. If it is used in a MultiCluster environment, it must either be set to the same value in all clusters, or not set in any cluster. Ensure that all binaries and libraries are upgraded to LSF Version 10.1 Fix Pack 11, including LSF_BINDIR, LSF_SERVERDIR, and LSF_LIBDIR directories, if you enable this parameter.
You must shut down the entire cluster before enabling or disabling this parameter.
If LSF_STRICT_CHECKING is defined, and your cluster has server hosts that are dynamically added, LSF_STRICT_CHECKING must be configured in the local lsf.conf file on all server hosts.
Valid values
Set to Y to enable strict checking of communications.
Set to ENHANCED to enable both checksum-secured authorization requests and strict checking of communications.
Set to N to disable both strict checking of communications and checksum-secured authorization requests. Only set to N if LSF is fully secure in a trusted environment.
Default
ENHANCED