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/13346 github. com/openstack/ nova/commit/ a694b9e5adec823 6ce8b2cd4832f8d c4912de6fc
Committed: http://
Submitter: Jenkins
Branch: master
commit a694b9e5adec823 6ce8b2cd4832f8d c4912de6fc
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