Access to jobs belonging to other users

All LSF jobs are run under the user ID of the user who submitted the job (unless you are using account mapping). LSF enforces restrictions on job access based on the user ID of the user who is running a command and the user ID associated with the submitted job.

All LSF users can view basic information on all jobs, including jobs submitted by other users, but can only view detailed information on or modify jobs submitted by their own user IDs. Only administrators can modify jobs submitted by other users.

User commands providing information on all jobs

Any LSF user can run the following commands to view basic information on any jobs running in the cluster, including jobs submitted by other users:

bjobs: displays information about LSF jobs. By default, bjobs displays information about your own pending, running, and suspended jobs. You can view information on jobs submitted by other users by using the -u option to specify a specific user, user group, or all users (using the all keyword).
bhist: displays historical information about LSF jobs. By default, bhist displays historical information about your own pending, running, and suspended jobs. You can view historical information on jobs submitted by other users by using the -u option to specify a specific user, user group, or all users (using the all keyword).
bhosts: displays information on hosts, including job state statistics and job slot limits. By default, you can view the number of jobs running on each host, including jobs submitted by other users; however, you only see the total number of jobs running on the host, not the specific users who submitted the jobs.
bqueues: displays information on queues, including job slot statistics and job state statistics. By default, the user can view the number of jobs running in each queue, including jobs submitted by other users; however, you only see the total number of jobs running in the queue, not the specific users who submitted the jobs.

User commands that restrict information on jobs submitted by other users

Any LSF user can run the following command to provide detailed information on jobs running in the cluster, but not on jobs submitted by other users:

bpeek: displays standard output and standard error output that have been produced by unfinished jobs. This command displays detailed information on the progress of a job, but you can only view jobs that belong to your own user ID.

Queue and administrator commands that modify all jobs

Queue administrators and LSF administrators can run the following commands to modify jobs submitted by any user. LSF users can also run these commands, but only to modify their own jobs with certain restrictions:

bbot: moves a pending job relative to the last job in the queue.
btop: moves a pending job relative to the first job in the queue.

LSF administrator commands that modify all jobs

LSF administrators can run the following commands to modify jobs submitted by any user. LSF users can also run these commands, but only to modify or control their own jobs with certain restrictions:

bchkpnt: Checkpoints one or more checkpointable jobs. LSF administrators can checkpoint jobs submitted by any user.
bkill: Sends a signal to kill unfinished jobs.
bmod: Modifies job submission options of a job.
brestart: Restarts checkpointed jobs.
bresume: Resumes a suspended job.
bstop: Suspends unfinished jobs.

Job data files

Jobs running in the LSF cluster inherit the environment from the user that submitted the job. Work files and output files are created based on the file permissions environment of the user (such as umask in POSIX environments). LSF does not provide additional security to these files. Therefore, to increase the security of work and output data, you need update the security of your hosts and file system according to the operating systems on your hosts.