-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/03/14 21:23, Marcin Stolarek wrote:
> bf_max_job_user=#
We already do this, but it doesn't change the state of the skipped
jobs to reflect the fact that they're not eligible to start.
cheers,
Chris
- --
Christopher SamuelSenior Syst
2014-03-03 23:46 GMT+01:00 Christopher Samuel :
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 04/03/14 04:53, Lyn Gerner wrote:
>
> > Have you also set AccountingStorageEnforce appropriately, as
> > described here: http://slurm.schedmd.com/resource_limits.html ?
>
> We've had the asso
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/03/14 04:53, Lyn Gerner wrote:
> Have you also set AccountingStorageEnforce appropriately, as
> described here: http://slurm.schedmd.com/resource_limits.html ?
We've had the association one from the start (we rely on hard limits
for CPU time f
Hi Chris,
Have you also set AccountingStorageEnforce appropriately, as described
here: http://slurm.schedmd.com/resource_limits.html ?
Best,
Lyn
On Sun, Mar 2, 2014 at 8:03 PM, Christopher Samuel wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 03/03/14 12:01, Christopher Samu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/03/14 12:01, Christopher Samuel wrote:
> and I can see the expected values when I do:
>
> # sacctmgr show assoc where cluster=barcoo account=foo
>
> but it doesn't appear to have any effect. I've tried restarting
> slurmctld on the node ju
