LSF Version 7.3 - Platform LSF Configuration Reference

Configuration file Parameter and syntax Default behavior
lsb.params
SYSTEM_MAPPING_ACCOUNT=
account
•
Enables Windows workgroup account
mapping
•
Windows local user accounts run LSF jobs
using the system account name and
permissions
Between-host user account mapping behavior
Local user account mapping example
The following example describes how local user account mapping works when configured in
the file .lsfhosts in the user’s home directory. Only mappings configured in .lsfhosts
on both the local and remote hosts work.
In the following example, the cluster contains hostA, hostB, and hostC. The account user1 is
valid on all hosts except hostC, which requires a user account name of user99.
To allow …
On … In the home
directory of
…
.lsfhosts must contain the line …
The account user1 to run jobs on all hosts
within the cluster:
•
user1 to send jobs to user99 on hostC
hostA user1
hostC user99 send
hostB user1
hostC user99 send
•
user99 to receive jobs from user1 on
either hostA or hostB
hostC user99
hostA user1 recv
hostB user1 recv
Windows workgroup account mapping example
The following example describes how Windows workgroup account mapping works when
configured in the file lsb.params. In this example, the cluster has a Windows workgroup
environment, and only the user account jobuser is valid on all hosts.
To allow …
In lsb.params, configure … Behavior
All hosts within the cluster to run
jobs on any other host within the
cluster:
•
Map all local users to user
account jobuser
SYSTEM_MAPPING_ACCOUNT=jobuser
When any local user submits an LSF
job, the job runs under the account
jobuser, using the permissions
associated with the jobuser account.
Configuration to modify between-host user account mapping
behavior
Not applicable: There are no parameters that modify the behavior of this feature.
Feature: Between-host user account mapping
10 Platform LSF Configuration Reference