Python ignores SIGPIPE on startup, because it prefers to check every
write and raise an IOError exception rather than taking the signal. Most
Unix subprocesses don't expect to work this way. This patch (adapted
from Colin Watson's post at http://tinyurl.com/2a7mzh5) sets SIGPIPE
back to the default action for quantum.agent.linux.utils.execute,
quantum.common.utils.execute and quantum-rootwrap created subprocesses.
Reviewed: https:/ /review. openstack. org/13348 github. com/openstack/ quantum/ commit/ 30fe8a4e3c53438 bbfb24ba882b3a3 7c65440e72
Committed: http://
Submitter: Jenkins
Branch: master
commit 30fe8a4e3c53438 bbfb24ba882b3a3 7c65440e72
Author: Thierry Carrez <email address hidden>
Date: Thu Sep 20 14:42:53 2012 +0200
Restore SIGPIPE default action for subprocesses
Python ignores SIGPIPE on startup, because it prefers to check every tinyurl. com/2a7mzh5) sets SIGPIPE agent.linux. utils.execute, common. utils.execute and quantum-rootwrap created subprocesses.
write and raise an IOError exception rather than taking the signal. Most
Unix subprocesses don't expect to work this way. This patch (adapted
from Colin Watson's post at http://
back to the default action for quantum.
quantum.
Fixes bug 1053364
Change-Id: Ib805f1f8846c24 5b75a5ea64278c8 40b823c1fb2