Platform LSF Reference Version 6.2

Limit Section
Platform LSF Reference
440
Use the not operator (~) to exclude queues from the all specification in the limit. This
is useful if you have a large number of queues but only want to exclude a few queues
from the limit definition.
In vertical tabular format, multiple queue names must be enclosed in parentheses.
In vertical tabular format, use empty parentheses
() or a dash (-) to indicate each
queue. Fields cannot be left blank.
Default
None. If no limit is specified for PER_QUEUE or QUEUES, no limit is enforced on
any queue.
Example PER_QUEUE=priority night
PER_USER
Syntax
PER_USER=all
[~]user_name ... | all [~]user_group ...
PER_USER
(
[-] | all [~]user_name ... | all [~ ]user_group ... )
Description
A space-separated list of user names or user groups on which limits are enforced. Limits
are enforced on each user or individually to each user in the user group listed. If a user
group contains a subgroup, the limit also applies to each member in the subgroup
recursively.
User names must be valid login names. User group names can be LSF user groups or
UNIX and Windows user groups. Note that for LSF and UNIX user groups, the groups
must be specified in
lsb.users first. See “UserGroup Section” on page 466.
Do not configure PER_USER and USERS limits in the same Limit section.
In horizontal format, use only one PER_USER line per Limit section.
Use the keyword
all to configure limits that apply to each user in a cluster. If user
groups are configured, the limit applies to each member of the user group, not the group
as a whole.
Use the not operator (
~) to exclude users or user groups from the all specification in
the limit. This is useful if you have a large number of users but only want to exclude a
few users from the limit definition.
In vertical tabular format, multiple user names must be enclosed in parentheses.
In vertical tabular format, use empty parentheses
() or a dash (-) to indicate user or
user group member. Fields cannot be left blank.
Default
None. If no limit is specified for PER_USER or USERS, no limit is enforced on any
user or user group.
Example PER_USER=user1 user2 ugroup1 ~user3
PROJECTS
Syntax
PROJECTS=all
[~]project_name ..
PROJECTS
(
[-] | all [~]project_name ...)