>> Am 16.11.2015 um 14:14 schrieb Winkler, Ursula (ursula.wink...@uni-graz.at)
>> :
>>
Am 16.11.2015 um 11:41 schrieb Winkler, Ursula
(ursula.wink...@uni-graz.at) :
Dear gridengine members,
when there are two queues and one is a subordinate of the other,
the
> Am 16.11.2015 um 14:14 schrieb Winkler, Ursula (ursula.wink...@uni-graz.at)
> :
>
>>> Am 16.11.2015 um 11:41 schrieb Winkler, Ursula (ursula.wink...@uni-graz.at)
>>> :
>>>
>>> Dear gridengine members,
>>>
>>> when there are two queues and one is a subordinate of the other, then
>>> the rel
>> Am 16.11.2015 um 11:41 schrieb Winkler, Ursula (ursula.wink...@uni-graz.at)
>> :
>>
>> Dear gridengine members,
>>
>> when there are two queues and one is a subordinate of the other, then
>> the release/shift of slots to the superordinate jobs is no problem,
>> but (other) consumeable resou
> Am 16.11.2015 um 11:41 schrieb Winkler, Ursula (ursula.wink...@uni-graz.at)
> :
>
> Dear gridengine members,
>
> when there are two queues and one is a subordinate of the other, then the
> release/shift
> of slots to the superordinate jobs is no problem, but (other) consumeable
> resources
Dear gridengine members,
when there are two queues and one is a subordinate of the other, then the
release/shift
of slots to the superordinate jobs is no problem, but (other) consumeable
resources
like h_vmem are. Does somebody have an idea to bypass that?
Thanks,
Ursula
___
