> Am 31.01.2020 um 18:23 schrieb Jerome IBt :
>
> Le 31/01/2020 à 10:19, Reuti a écrit :
>> Hi Jérôme,
>>
>> Personally I would prefer to keep the output of `qquota` short and use it
>> only for users's limits. I.e. defining the slot limit on an exechost basis
>> instead. This can also be
Le 31/01/2020 à 10:19, Reuti a écrit :
> Hi Jérôme,
>
> Personally I would prefer to keep the output of `qquota` short and use it
> only for users's limits. I.e. defining the slot limit on an exechost basis
> instead. This can also be done in a loop containing a command line like:
>
> $ qconf
Hi Jérôme,
Personally I would prefer to keep the output of `qquota` short and use it only
for users's limits. I.e. defining the slot limit on an exechost basis instead.
This can also be done in a loop containing a command line like:
$ qconf -mattr exechost complex_values slots=16 node29
My
Dear all
I'm facing a new problem on my cluster with SGE. I don't show this
before.. O maybe I never detect it.
I have some nodes with 2 queue, one (named "all.q" ) to run jobs no more
than 24h , and another queue (named "lenta.q" ) to run jobs than need
more than 24 h.
I determine qa resource