From 23cc6611c8b5303ec2ecf8cb8203e69ddb825551 Mon Sep 17 00:00:00 2001 From: Zac Medico Date: Mon, 31 Jan 2011 20:33:48 -0800 Subject: EbuildFetcher: use default SIGINT/TERM handlers This seems to fix bug #353239. --- pym/_emerge/EbuildFetcher.py | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'pym/_emerge/EbuildFetcher.py') diff --git a/pym/_emerge/EbuildFetcher.py b/pym/_emerge/EbuildFetcher.py index 59076a8db..0ea8dc775 100644 --- a/pym/_emerge/EbuildFetcher.py +++ b/pym/_emerge/EbuildFetcher.py @@ -5,6 +5,7 @@ import traceback from _emerge.SpawnProcess import SpawnProcess import copy +import signal import sys import portage from portage import os @@ -95,6 +96,11 @@ class EbuildFetcher(SpawnProcess): portage.process._setup_pipes(fd_pipes) + # Use default signal handlers in order to avoid problems + # killing subprocesses as reported in bug #353239. + signal.signal(signal.SIGINT, signal.SIG_DFL) + signal.signal(signal.SIGTERM, signal.SIG_DFL) + # Force consistent color output, in case we are capturing fetch # output through a normal pipe due to unavailability of ptys. portage.output.havecolor = self._settings.get('NOCOLOR') \ -- cgit v1.2.3-1-g7c22