25.06.2015 Views

Administering Platform LSF - SAS

Administering Platform LSF - SAS

Administering Platform LSF - SAS

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Mail Notification When a Job Starts<br />

Mail Notification When a Job Starts<br />

bsub mail options<br />

When a batch job completes or exits, <strong>LSF</strong> by default sends a job report by<br />

electronic mail to the submitting user account. The report includes the<br />

following information:<br />

◆ Standard output (stdout) of the job<br />

◆ Standard error (stderr) of the job<br />

◆ <strong>LSF</strong> job information such as CPU, process and memory usage<br />

The output from stdout and stderr are merged together in the order printed,<br />

as if the job was run interactively. The default standard input (stdin) file is the<br />

null device. The null device on UNIX is /dev/null.<br />

-B Sends email to the job submitter when the job is dispatched and begins<br />

running. The default destination for email is defined by LSB_MAILTO in<br />

lsf.conf.<br />

-u user_name If you want mail sent to another user, use the -u user_name option to the<br />

bsub command. Mail associated with the job will be sent to the named user<br />

instead of to the submitting user account.<br />

-N If you want to separate the job report information from the job output, use the<br />

-N option to specify that the job report information should be sent by email.<br />

-o and -e Options The output file created by the -o option to the bsub command normally<br />

contains job report information as well as the job output. This information<br />

includes the submitting user and host, the execution host, the CPU time (user<br />

plus system time) used by the job, and the exit status.<br />

If you specify a -o output_file option and do not specify a -e error_file<br />

option, the standard output and standard error are merged and stored in<br />

output_file. You can also specify the standard input file if the job needs to<br />

read input from stdin.<br />

The output files specified by the -o and -e options are created on the<br />

execution host.<br />

See “Remote File Access” on page 516 for an example of copying the output<br />

file back to the submission host if the job executes on a file system that is not<br />

shared between the submission and execution hosts.<br />

Disabling job<br />

email<br />

If you do not want job output to be sent by mail, specify stdout and stderr<br />

as the files for -o and -e. For example, the following command directs stderr<br />

and stdout to file named /tmp/job_out, and no email is sent.<br />

bsub -o /tmp/job_out sleep 5<br />

On UNIX, If you want no job output or email at all, specify /dev/null as the<br />

output file:<br />

bsub -o /dev/null sleep 5<br />

506<br />

<strong>Administering</strong> <strong>Platform</strong> <strong>LSF</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!