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 cinder.utils.execute and cinder-rootwrap
created subprocesses.
Reviewed: https:/ /review. openstack. org/13347 github. com/openstack/ cinder/ commit/ 730ebab71e11812 b6b5990180e7bd9 cabfe237c4
Committed: http://
Submitter: Jenkins
Branch: master
commit 730ebab71e11812 b6b5990180e7bd9 cabfe237c4
Author: Thierry Carrez <email address hidden>
Date: Thu Sep 20 14:21:00 2012 +0200
Restore SIGPIPE default action for subprocesses
Python ignores SIGPIPE on startup, because it prefers to check every tinyurl. com/2a7mzh5) sets SIGPIPE utils.execute and cinder-rootwrap
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 cinder.
created subprocesses.
Fixes bug 1053364
Change-Id: I4b3307bd2f0f5d 0da529d8b7d80fa bae28c57732