job_aborting+ed event

[tarekziade]

When the worker receives a signal that makes it quit the current job, like SIGUSR1, we need to give a chance to the user to do something in its code.

I propose two events:

• job_aborting - triggered at the beginning of kill_child() if there's a running job in the worker
• job_aborted - triggered after kill_child()

What do you think ?

[bbangert]

Wouldn't a general shut-down event handle job_aborted? Or perhaps setting a variable during job_aborting that the on quit handler can see.

[tarekziade]

sounds good