LSF Version 7.3 - Platform LSF Configuration Reference

Jobs that do not match these limits; that is, all users except user1 and user3 running jobs
on hostA and all users except user2 submitting jobs to queue normal, have no limits.
Horizontal format
All users in user group ugroup1 except user1 using queue1 and queue2 and running jobs
on hosts in host group hgroup1 are limited to 2 job slots per processor on each host:
Begin Limit
# ugroup1 except user1 uses queue1 and queue2 with 2 job slots
# on each host in hgroup1
NAME = limit1
# Resources
SLOTS_PER_PROCESSOR = 2
#Consumers
QUEUES = queue1 queue2
USERS = ugroup1 ~user1
PER_HOST = hgroup1
End Limit
Compatibility with lsb.queues, lsb.users, and lsb.hosts
The Limit section of lsb.resources does not support the keywords or format used in
lsb.users, lsb.hosts, and lsb.queues. However, your existing job slot limit
configuration in these files will continue to apply.
Job slot limits are the only type of limit you can configure in lsb.users, lsb.hosts, and
lsb.queues. You cannot configure limits for user groups, host groups, and projects in
lsb.users, lsb.hosts, and lsb.queues. You should not configure any new resource
allocation limits in lsb.users, lsb.hosts, and lsb.queues. Use lsb.resources to
configure all new resource allocation limits, including job slot limits. Limits on running and
suspended jobs can only be set in lsb.resources.
Existing limits in lsb.users, lsb.hosts, and lsb.queues with the same scope as a new
limit in lsb.resources, but with a different value are ignored. The value of the new limit
in lsb.resources is used. Similar limits with different scope enforce the most restrictive
limit.
Parameters
•
HOSTS
•
JOBS
•
LICENSE
•
MEM
•
NAME
•
PER_HOST
•
PER_PROJECT
•
PER_QUEUE
•
PER_USER
•
PROJECTS
•
QUEUES
•
RESOURCE
•
SLOTS
•
SLOTS_PER_PROCESSOR
•
SWP
•
TMP
lsb.resources
Platform LSF Configuration Reference 327