Skip to content
Snippets Groups Projects
Commit 34275f9c authored by Moe Jette's avatar Moe Jette
Browse files

clarify salloc handling of signals

parent 16e2f214
No related branches found
No related tags found
No related merge requests found
......@@ -1077,12 +1077,12 @@ The block name on Blue Gene systems only.
While salloc is waiting for a PENDING job allocation, most signals will cause
salloc to revoke the allocation request and exit.
However, if the allocation has been granted and salloc has already started the
command specified in its command line parameters salloc will ignore most
signals. salloc will not exit or release the allocation until the command
exits. One notable exception is SIGHUP; a HUP signal will cause salloc to
However if the allocation has been granted and salloc has already started the
specified command, then salloc will ignore most signals.
salloc will not exit or release the allocation until the command exits.
One notable exception is SIGHUP. A SIGHUP signal will cause salloc to
release the allocation and exit without waiting for the command to finish.
Another exception is SIGTERM, which will be forwarded to the spawned program.
Another exception is SIGTERM, which will be forwarded to the spawned process.
.SH "EXAMPLES"
.LP
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment