1. 02 Aug, 2018 1 commit
  2. 31 Jul, 2018 1 commit
  3. 27 Jul, 2018 3 commits
  4. 24 Jul, 2018 1 commit
  5. 19 Jul, 2018 4 commits
  6. 18 Jul, 2018 4 commits
  7. 17 Jul, 2018 5 commits
  8. 13 Jul, 2018 1 commit
  9. 12 Jul, 2018 3 commits
  10. 09 Jul, 2018 1 commit
  11. 06 Jul, 2018 1 commit
    • Marshall Garey's avatar
      Fix leaking freezer cgroups. · 7f9c4f73
      Marshall Garey authored
      Continuation of 923c9b37.
      
      There is a delay in the cgroup system when moving a PID from one cgroup
      to another. It is usually short, but if we don't wait for the PID to
      move before removing cgroup directories the PID previously belonged to,
      we could leak cgroups. This was previously fixed in the cpuset and
      devices subsystems. This uses the same logic to fix the freezer
      subsystem.
      
      Bug 5082.
      7f9c4f73
  12. 05 Jul, 2018 1 commit
  13. 04 Jul, 2018 2 commits
  14. 03 Jul, 2018 2 commits
  15. 26 Jun, 2018 4 commits
  16. 25 Jun, 2018 1 commit
  17. 22 Jun, 2018 2 commits
  18. 20 Jun, 2018 2 commits
  19. 19 Jun, 2018 1 commit
    • Isaac Hartung's avatar
      Don't enforce MaxQueryTimeRange with specific jobs · d41cb31a
      Isaac Hartung authored
      When requesting specific jobids with sacct, the starttime of the request
      is 0, which will cause the time range to be outside of the
      MaxQueryTimeRange range -- if specified. When requesting specific
      jobids, sacct should be able to find the job whenever it started --
      unless confined to a smaller range with -S and/or -E.
      
      Bug 5009
      d41cb31a