What if make possible sygnals configurable via constructor? It could accept an array of posix signals which would stop the worker.

For example in my project, we terminate workers with SIGQUIT and for it to work I had to create a new listener

@lyrixx wdyt?

How Would you configure the subscriber ?

@lyrixx like this. Except $signal could be int[] instead, then onWorkerStarted would simply iterate and call pcntl_signal

final class StopWorkerOnPcntlSignalListener implements EventSubscriberInterface
{
    public function __construct(private readonly int $signal) {}

    public static function getSubscribedEvents(): array
    {
        return [WorkerStartedEvent::class => ['onWorkerStarted', 100]];
    }

    public function onWorkerStarted(WorkerStartedEvent $event): void
    {
        pcntl_signal(
            $this->signal,
            static function () use ($event): void {
                $event->getWorker()->stop();
            },
        );
    }
}

Sorry, I was not clear. With Symfony full stack, this service is not created by you, but by the framework. So how would you configure it? I think we can set some sane defaults, then if you want other signals, you replace the services arguments. Are you OK with this? I'll do the PR ASAP

I opened a PR ☝