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

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

Open
@teake

Description

@teake

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions