Re-reading the man page yet another time made me think that this is the
desired and logical behavior: if the job id remains the same, then h_rt and
s_rt counters cannot be reset: job starts only once, execution *continues*
after re-scheduing:
"RESOURCE LIMITS
The first two resource limit pa
> Am 11.06.2018 um 18:43 schrieb Ilya M <4ilya.m+g...@gmail.com>:
>
> Hello,
>
> Thank you for the suggestion, Reuti. Not sure if my users' pipelines can deal
> with multiple job ids, perhaps they will be willing to modify their code.
Also other commands in SGE like `qdel` allow to use the jo
Hello,
Thank you for the suggestion, Reuti. Not sure if my users' pipelines can
deal with multiple job ids, perhaps they will be willing to modify their
code.
On Mon, Jun 11, 2018 at 9:23 AM, Reuti wrote:
> Hi,
>
>
> I wouldn't be surprised if the execd remembers that the job was already
> warn
Hi,
> Am 08.06.2018 um 23:46 schrieb Ilya M <4ilya.m+g...@gmail.com>:
>
> Hello,
>
> I found an unexpected behavior when setting a hard and soft time limits and
> doing automatic rescheduling by SIGUSR1.
I wouldn't be surprised if the execd remembers that the job was already warned,
hence it
Hi,
> Am 11.06.2018 um 12:04 schrieb Jakub pl :
>
> Dear all,
>
> I have a problem with my grid engine. I have a queue with assigned project
> name. When I submit a job with -P project name, and there are free slots is
> queue, job is scheduled as expected. But when there is no slots, job -
>
Dear all,
I have a problem with my grid engine. I have a queue with assigned project
name. When I submit a job with -P project name, and there are free slots is
queue, job is scheduled as expected. But when there is no slots, job -
instead of waiting is being scheduled to default queue(with no pro
