- Apr 07, 2011
-
-
Moe Jette authored
can be found in the user's default search path. Modify slurmstepd to find the executable. Patch from Andrej Gritsenko.
-
Moe Jette authored
of leaving in UNKNOWN+POWER. Patch from Andrej Gritsenko.
-
Danny Auble authored
Fix so slurmctld will pack correctly 2.1 step information. (Only needed if a 2.1 client is talking to a 2.2 slurmctld.)
-
Danny Auble authored
-
- Apr 06, 2011
-
-
Don Lipari authored
-
Don Lipari authored
-
- Apr 05, 2011
- Apr 04, 2011
- Apr 02, 2011
-
-
Moe Jette authored
Avoid filling slurmd logs about unkillable jobs.
-
- Apr 01, 2011
-
-
Moe Jette authored
damon that should be running on the node is not running. Patch from Rod Schulz, Bull.
-
- Mar 31, 2011
- Mar 30, 2011
-
-
Moe Jette authored
-
Moe Jette authored
-
Moe Jette authored
-
Danny Auble authored
BLUEGENE - Added back a lock when creating dynamic blocks to be more thread safe on larger systems with heavy load.
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
Fix associations/qos for when adding back a previously deleted object the object will be cleared of all old limits.
-
Danny Auble authored
-
Moe Jette authored
-
- Mar 29, 2011
-
-
Moe Jette authored
The man page for slurm.conf, select/cons_res parameter SelectTypeParameters, values CR_Socket and CR_Socket_Memory states the following: "Note that jobs requesting one CPU will only be given access to that one CPU" I think this statement is incorrect, or at least very misleading to users. A job requesting one CPU will only be allocated one CPU, but unless task/affinity is enabled or some other CPU binding mechanism is used, the job can access all of the CPUs on the node. That is, a task that is distributed to the node can run on any of the CPUs on the node, not just on the one CPU that was allocated to its job. I propose the following patch to replace "given access to" with "allocated". Regards, Martin Perry
-
- Mar 28, 2011
-
-
Moe Jette authored
-
- Mar 25, 2011
-
-
Danny Auble authored
Fix cosmetic sacctmgr issue where if the user you are trying to add doesn't exist in the /etc/passwd file and the account you are trying to add them to doesn't exist it would print (null) instead of the bad account name.
-
- Mar 24, 2011
-
-
Moe Jette authored
-
- Mar 23, 2011
-
-
Moe Jette authored
Fixes bug reported by Bill Brophy, Bull.
-
Moe Jette authored
-
Moe Jette authored
-
Moe Jette authored
Dennis Leepow.
-
Moe Jette authored
-
Moe Jette authored
as UID values. Patch from Dennis Leepow.
-
Moe Jette authored
a constraint field with a count (e.g. "srun --constraint=gpu*2 -N4 a.out").
-
Moe Jette authored
-
- Mar 22, 2011
-
-
Danny Auble authored
-
Moe Jette authored
The change resulted in some cases where job steps were allocated zero CPUs on some nodes.
-
- Mar 21, 2011