On 20/02/16 04:24, Skouson, Gary B wrote: > When I tried that, it looks like I end up with a default of > maxjobs=<whatever> for each of the account/user associations.
Hmm, we've just gone into an outage window (for GPFS and electrical work) and that was something I was about to roll out. Looking at the test system it appears that maxjob is indeed per association, and the sacctmgr does not list MaxJob as a property that a user can have, it only appears via associations (as you can see if you use the -s option to sacctmgr when listing a user). It's not a problem for us as we consider that if a user is working on two different projects then they are acting as an agent of the project and so should be able to run jobs for both without one interfering with the other. But yes, I can see that as inconvenient to sites with different policies! :-( All the best, Chris -- Christopher Samuel Senior Systems Administrator VLSCI - Victorian Life Sciences Computation Initiative Email: [email protected] Phone: +61 (0)3 903 55545 http://www.vlsci.org.au/ http://twitter.com/vlsci
