- 02 Jan, 2018 3 commits
-
-
Morris Jette authored
-
Morris Jette authored
Bug 4529
-
Danny Auble authored
Bug 4564
-
- 28 Dec, 2017 3 commits
-
-
Tim Wickberg authored
-
Tim Wickberg authored
_run_prog() executes after a fork(), if some thread in the parent was holding slurm_conf_lock() it would never be released, and the child will deadlocked. Already fixed for 17.11 by commit e205eeaf, this backports just the change for _run_prog(). Bug 4562.
-
Brian Christiansen authored
-
- 27 Dec, 2017 12 commits
-
-
Danny Auble authored
Bug 4529
-
Danny Auble authored
instead of the normal comment. Also send it to the database if needed. Bug 4529
-
Danny Auble authored
as well as updating the system_comment. Bug 4529
-
Danny Auble authored
before returning. Bug 4529
-
Danny Auble authored
Bug 4529
-
Danny Auble authored
-
Danny Auble authored
Bug 4529
-
Danny Auble authored
Bug 4529
-
Danny Auble authored
Bug 4529
-
Danny Auble authored
No real code change. Bug 4529
-
Danny Auble authored
Bug 4529
-
Danny Auble authored
-
- 22 Dec, 2017 5 commits
-
-
Alejandro Sanchez authored
The ability to enforce strict content-type checking has existed since Elasticsearch 5.3 via the http.content_type.required configuration setting. In 5.x it is optional, and defaults to false, in Elasticsearch 6.0, that setting defaults to true, and there is no way to disable it. If required and not appended, Elasticsearch would response with status 406, so "Content-Type: application/json" is appended from now on. Tested against Elasticsearch 5.5.1 and 6.1.1. Bug reported to slurm-users list from E.S. Rosenberg. Patch suggested didn't check the return code of curl_slist_append() and didn't free the slist.
-
Morris Jette authored
Bug 4537
-
Tim Wickberg authored
-
Tim Wickberg authored
Update slurm.spec and slurm.spec-legacy as well
-
Danny Auble authored
Bug 4551,4553
-
- 20 Dec, 2017 17 commits
-
-
Tim Wickberg authored
-
Tim Wickberg authored
Update slurm.spec and slurm.spec-legacy as well
-
Danny Auble authored
# Conflicts: # src/plugins/task/cgroup/task_cgroup_cpuset.c
-
Tim Wickberg authored
-
Danny Auble authored
-
Danny Auble authored
-
Alejandro Sanchez authored
This mostly reverts commit 8325e9f8. Bug 4478 We decided to not do this by default for the slurmd. See bug 4478 for more info/reasoning. We also didn't want to rely on #include <linux/oom.h> since that might not exist everywhere.
-
Tim Wickberg authored
Format for inserted X11 cookies is now hostname/unix:display, rather than localhost:display. This seems to resolve some issues for different setups while not causing any issues in my test environments. This also helps avoid a conflict between multiple nodes in a larger job if the same display number is allocated on multiple nodes simultaneously. Bug 4420.
-
Danny Auble authored
Bug 4483
-
Boris Karasev authored
Signed-off-by:
Boris Karasev <karasev.b@gmail.com>
-
Danny Auble authored
Bug 4541
-
Danny Auble authored
The slurm and pmix RPMs both attempt to install a libpmi. While Slurm's version should be preferred, the best way to handle this is to have both pmix and slurm packages split this off into a separate RPM that can conflict with each other, giving the admin a way to resolve the conflict manually. Bug 4511.
-
Brian Christiansen authored
The cluster name could have been free'd before it would be strdup'ed. Happens when a federated persisent connection is established and the cluster needs to sync up with the remote cluster. Bug 4503
-
Brian Christiansen authored
Remove the origin job when a remote sibling job was cancelled while the origin was down. e.g. job originated on cluster1 job runs on cluster2 cluster1 goes down job is cancelled on cluster2 cluster1 comes backup. The origin job should be removed if the sibling job was cancelled.
-
Morris Jette authored
Replace some references to "pack job" with "heterogenous job". bug 4546
-
Tim Wickberg authored
The user_name is only populated if LaunchParameters=send_gids is set. Without this field set, the pam_setup call will get NULL instead of the user_name, leading to batch job launch failures. (The step launch code already handles this same issue separately.) Bug 4412.
-
Morris Jette authored
-