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/14084 github. com/openstack/ quantum/ commit/ 3bbf281b15866fc 6aecdf8283bca69 6e5c646300
Committed: http://
Submitter: Jenkins
Branch: stable/folsom
commit 3bbf281b15866fc 6aecdf8283bca69 6e5c646300
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