Am 30.11.2011 um 12:12 schrieb baf035:
> Yes, SIGUSR1 is globaly blocked; inside of a GE starter method is added a
> line "signal (SIGUSR1, SIG_IGN);"
> I consider as a weirdness that in the master node execd messages is a
> recorded exceeded hard walclock time:
>
> "11/29/2011 14:06:33| main
Am 29.11.2011 um 17:37 schrieb baf035:
> Hello Reuti,
>
> thanks for a clarification, I probably misunderstand man pages and used both
> parameters: s_rt and -notify together before.
>
> Our goal is to configure exactly working backfilling. We use for s_rt a mean
> value of running time of fin
Hello Reuti,
thanks for a clarification, I probably misunderstand man pages and used
both parameters: s_rt and -notify together before.
Our goal is to configure exactly working backfilling. We use for s_rt a
mean value of running time of finished jobs based on their category.
In a queue configura
Hi,
Am 22.11.2011 um 12:58 schrieb baf035:
>
> Hello all.
>
> 1) When s_rt time is reached a job is signaled by default by SIGUSR1. One of
> our applications is dying by the signal.
> I changed in a global configuration in execd_params a parameter
> NOTIFY_KILL=none or NOTIFY_KILL=SIGCONT
> b
Hello all.
1) When s_rt time is reached a job is signaled by default by SIGUSR1. One
of our applications is dying by the signal.
I changed in a global configuration in execd_params a parameter
NOTIFY_KILL=none or NOTIFY_KILL=SIGCONT
bur without effect. Applications are still signaled by SIGUSR1. H
