Skip to content
This repository has been archived by the owner on Apr 11, 2022. It is now read-only.

SIGQUIT doesn't always trigger Worker::shutdown() #17

Open
teake opened this issue Jun 25, 2015 · 0 comments
Open

SIGQUIT doesn't always trigger Worker::shutdown() #17

teake opened this issue Jun 25, 2015 · 0 comments
Labels

Comments

@teake
Copy link
Contributor

teake commented Jun 25, 2015

I'm seeing strange behaviour upon sending a SIGQUIT signal to a worker. If the worker is instantiated as follows:

$resque = new \Resque\Resque(<some client>);
$worker = new \Resque\Worker($resque);

then the SIGQUIT doesn't trigger a call to $worker->shutdown(). However, if it is instantiated as follows:

$worker = new \Resque\Worker(new \Resque\Resque(<some client>));

then the SIGQUIT does trigger a call to $worker->shutdown(). Strangely enough, doing the following:

$resque = new \Resque\Resque(<some client>);
$resque->setLogger(<some logger>);
$worker = new \Resque\Worker($resque);

then the SIGQUIT again behaves as expected and triggers a call to $worker->shutdown().
Any idea what's going on?

@dominics dominics added the bug label Jun 30, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants