- 26 Jun, 2012 4 commits
-
-
Danny Auble authored
-
Danny Auble authored
bg.properties in order for the runjob_mux to run correctly. Signed-off-by: Danny Auble <da@schedmd.com>
-
Danny Auble authored
but job is going to be canceled because it is interactive or other reason it now receives the grace time.
-
Morris Jette authored
-
- 25 Jun, 2012 3 commits
-
-
Danny Auble authored
check if a block is still makable if the cable wasn't in error.
-
Danny Auble authored
removal of the job on the block failed.
-
Danny Auble authored
-
- 22 Jun, 2012 3 commits
-
-
Danny Auble authored
29d79ef8
-
Danny Auble authored
same time a block is destroyed and that block just happens to be the smallest overlapping block over the bad hardware.
-
Danny Auble authored
-
- 20 Jun, 2012 2 commits
-
-
Danny Auble authored
but not node count the node count is correctly figured out.
-
Morris Jette authored
Without this fix, gang scheduling mode could start without creating a list resulting in an assert when jobs are submitted.
-
- 18 Jun, 2012 2 commits
-
-
Danny Auble authored
packing the step layout structure.
-
Danny Auble authored
we must use a small block instead of a shared midplane block.
-
- 15 Jun, 2012 1 commit
-
-
Danny Auble authored
-
- 13 Jun, 2012 2 commits
-
-
Danny Auble authored
still messages we find when we poll but haven't given it back to the real time yet.
-
Danny Auble authored
-
- 12 Jun, 2012 1 commit
-
-
Danny Auble authored
-
- 05 Jun, 2012 1 commit
-
-
Danny Auble authored
a job kill timeout aren't always reported to the system. This is now handled by the runjob_mux plugin.
-
- 03 Jun, 2012 1 commit
-
-
jette authored
-
- 01 Jun, 2012 2 commits
-
-
Danny Auble authored
sub-blocks.
-
Danny Auble authored
to make a larger small block and are running with sub-blocks.
-
- 31 May, 2012 1 commit
-
-
Danny Auble authored
function didn't always work correctly.
-
- 30 May, 2012 4 commits
-
-
Danny Auble authored
the next step in the allocation only uses part of the allocation it gets the correct cnodes.
-
Morris Jette authored
-
Andy Wettstein authored
In etc/init.d/slurm move check for scontrol after sourcing /etc/sysconfig/slurm. Patch from Andy Wettstein, University of Chicago.
-
Morris Jette authored
Change license option count separator from "*" to ":" for consistency with the gres option (e.g. "--licenses=foo:2 --gres=gpu:2"). The "*" will still be accepted, but is no longer documented.
-
- 29 May, 2012 4 commits
-
-
Danny Auble authored
maintain.
-
Don Lipari authored
-
Rod Schultz authored
This change makes the code consistent with the documentation. Note that "bf_res=" will continue to be recognized for now. Patch from Rod Schultz, Bull.
-
Don Albert authored
I have implemented the changes as you suggested: using a "-dd" option to indicate that the display of the script is wanted, and setting both the "SHOW_DETAIL" and a new "SHOW_DETAIL2" flag. Since "scontrol" can be run interactively as well, I added a new "script" option to indicate that display of both the script and the details is wanted if the job is a batch job. Here are the man page updates for "man scontrol". For the "-d, --details" option: -d, --details Causes the show command to provide additional details where available. Repeating the option more than once (e.g., "-dd") will cause the show job command to also list the batch script, if the job was a batch job. For the interactive "details" option: details Causes the show command to provide additional details where available. Job information will include CPUs and NUMA memory allocated on each node. Note that on computers with hyperthreading enabled and SLURM configured to allocate cores, each listed CPU represents one physical core. Each hyperthread on that core can be allocated a separate task, so a job's CPU count and task count may differ. See the --cpu_bind and --mem_bind option descriptions in srun man pages for more information. The details option is currently only supported for the show job command. To also list the batch script for batch jobs, in addition to the details, use the script option described below instead of this option. And for the new interactive "script" option: script Causes the show job command to list the batch script for batch jobs in addition to the detail informa- tion described under the details option above. Attached are the patch file for the changes and a text file with the results of the tests I did to check out the changes. The patches are against SLURM 2.4.0-rc1. -Don Albert-
-
- 25 May, 2012 2 commits
-
-
Rod Schultz authored
This change makes the code consistent with the documentation. Note that "bf_res=" will continue to be recognized for now. Patch from Rod Schultz, Bull.
-
Don Albert authored
I have implemented the changes as you suggested: using a "-dd" option to indicate that the display of the script is wanted, and setting both the "SHOW_DETAIL" and a new "SHOW_DETAIL2" flag. Since "scontrol" can be run interactively as well, I added a new "script" option to indicate that display of both the script and the details is wanted if the job is a batch job. Here are the man page updates for "man scontrol". For the "-d, --details" option: -d, --details Causes the show command to provide additional details where available. Repeating the option more than once (e.g., "-dd") will cause the show job command to also list the batch script, if the job was a batch job. For the interactive "details" option: details Causes the show command to provide additional details where available. Job information will include CPUs and NUMA memory allocated on each node. Note that on computers with hyperthreading enabled and SLURM configured to allocate cores, each listed CPU represents one physical core. Each hyperthread on that core can be allocated a separate task, so a job's CPU count and task count may differ. See the --cpu_bind and --mem_bind option descriptions in srun man pages for more information. The details option is currently only supported for the show job command. To also list the batch script for batch jobs, in addition to the details, use the script option described below instead of this option. And for the new interactive "script" option: script Causes the show job command to list the batch script for batch jobs in addition to the detail informa- tion described under the details option above. Attached are the patch file for the changes and a text file with the results of the tests I did to check out the changes. The patches are against SLURM 2.4.0-rc1. -Don Albert-
-
- 24 May, 2012 3 commits
-
-
Danny Auble authored
compiling with --enable-debug
-
Jon Bringhurst authored
The purpose of this is so moab scripts and commands (such as 'checkjob') have consistent access to the SUBMITHOST variable.
-
Danny Auble authored
-
- 23 May, 2012 4 commits
-
-
Danny Auble authored
-
Danny Auble authored
isn't up at the time the slurmctld starts, not running the priority/multifactor plugin, and then the database is started up later.
-
Morris Jette authored
-
Morris Jette authored
Format is "name:used/total"
-