- 10 Aug, 2006 1 commit
-
-
Moe Jette authored
-
- 09 Aug, 2006 5 commits
-
-
Christopher J. Morrone authored
-
Christopher J. Morrone authored
-
Christopher J. Morrone authored
Default behaviour is to print a message notifying the user. Also added the -K/--kill-command option, which tells salloc to send a signal to the user's command when a job-complete message arrives.
-
-
Moe Jette authored
-
- 08 Aug, 2006 7 commits
-
-
-
Moe Jette authored
-
Moe Jette authored
rather than slurm function).
-
Moe Jette authored
older tests.
-
Christopher J. Morrone authored
-
Christopher J. Morrone authored
-
Christopher J. Morrone authored
from the step context, and the assiciated allocation lookup rpc. Creating a step context now requires only a single RPC to the controller.
-
- 07 Aug, 2006 1 commit
-
-
Christopher J. Morrone authored
-
- 05 Aug, 2006 5 commits
-
-
Christopher J. Morrone authored
-
-
Danny Auble authored
-
-
Moe Jette authored
add tests for slaunch --debug and --verbose options
-
- 04 Aug, 2006 21 commits
-
-
Moe Jette authored
-
Moe Jette authored
-
-
Moe Jette authored
-
Moe Jette authored
-
Moe Jette authored
use output of function default_partition, otherwise use the partition explicitly named in your globals.local file
-
Moe Jette authored
-
Danny Auble authored
-
Moe Jette authored
response to job completion RPC.
-
Moe Jette authored
communication itself) fails
-
Danny Auble authored
-
Danny Auble authored
-
Moe Jette authored
-
Danny Auble authored
-
-
Christopher J. Morrone authored
If the allocation has been granted, it will release the job allocation on the first SIGINT, and ignore any following SIGINT signals while waiting for the user's command to exit. If the allocation if pending, salloc revokes the allocation and exits. Should all other signals have the same behaviour?
-
Christopher J. Morrone authored
-
Christopher J. Morrone authored
-
Christopher J. Morrone authored
-
Moe Jette authored
Required scontrol to use helper library.
-
Moe Jette authored
statically linked.
-