search

dmwm / CRAB2

CRAB2
2 stars 11 forks source link

trap all local batch interrrupts #1069

Closed belforte closed 10 years ago

belforte commented 10 years ago

currently crab wrapper only traps SIGUSR2 and SIGTERM but some batch system may also send SIGINT and others in particular CERN is 'famous' for sending SIGING see http://information-technology.web.cern.ch/services/fe/lxbatch/howto/how-interpet-batch-job-return-codes also try to print in the stdout which interrupt signal was received

belforte commented 10 years ago

ref: https://github.com/belforte/CRAB2/blob/master/python/crab_template.sh#L138

PerilousApricot commented 10 years ago

What a mess.

belforte commented 10 years ago

@PerilousApricot why ? I thought this to be simple, I forgot one signal and will add, tacking the chance to flag which signal was received. But maybe I am missing something

PerilousApricot commented 10 years ago

It would be nice if the batch scheduler sent the message to the wrapper script itself instead of one of its subprocesses.

belforte commented 10 years ago

maybe it does, but since crab does not trap it, the message gets passed down the chain. OTH.. what do I know of how these things really work ?

belforte commented 10 years ago

fix released in 2_10_4_patch4