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 nova.utils.execute and nova-rootwrap
created subprocesses.
Reviewed: https:/ /review. openstack. org/14085 github. com/openstack/ nova/commit/ d4d166503a93a45 8fabdcd919882d2 9fc590ad7b
Committed: http://
Submitter: Jenkins
Branch: stable/folsom
commit d4d166503a93a45 8fabdcd919882d2 9fc590ad7b
Author: Thierry Carrez <email address hidden>
Date: Thu Sep 20 14:11:38 2012 +0200
Restore SIGPIPE default action for subprocesses
Python ignores SIGPIPE on startup, because it prefers to check every tinyurl. com/2a7mzh5) sets SIGPIPE
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 nova.utils.execute and nova-rootwrap
created subprocesses.
Fixes bug 1053364
Change-Id: I17e1629bb4ef42 68515c6734ddb6e 12746739c52