Ressending just in case it got lost... On Wednesday, April 10, 2013, Chris Read wrote:
> Greetings all... > > We've just set the MaxCPUMins in a commonly used QOS with our users, and > expected DenyOnLimit to reject their job submissions if the number of CPU's > they requested * the timelimit they set was greater than this value. Turns > out it is not the case, and we had a load of jobs stuck in PENDING > QOSJobLimit. > > Based on my reading (and expectation) of the DenyOnLimit flag, if it's > possible that could end up pending on QOSJobLimit, then if DenyOnLimit is > set slurm should simply reject the job submission. > > I've submitted a pull request (https://github.com/SchedMD/slurm/pull/46) > with a patch that makes it work. > > Chris >
