On Fri, Jan 28, 2011 at 09:32:42AM -0700, Eric Blake wrote:
> On 01/24/2011 08:13 AM, Daniel P. Berrange wrote:
> > Some functionality run in virExec hooks may do I/O which
> > can trigger SIGPIPE. Renable SIGPIPE blocking around the
> > hook function
>
> > * src/util/util.c: Block SIGPIPE around
On 01/24/2011 08:13 AM, Daniel P. Berrange wrote:
> Some functionality run in virExec hooks may do I/O which
> can trigger SIGPIPE. Renable SIGPIPE blocking around the
> hook function
> * src/util/util.c: Block SIGPIPE around hooks
> -if (hook)
> +if (hook) {
> +/* virFork reset al
Some functionality run in virExec hooks may do I/O which
can trigger SIGPIPE. Renable SIGPIPE blocking around the
hook function
* src/util/util.c: Block SIGPIPE around hooks
---
src/util/util.c | 24 +++-
1 files changed, 23 insertions(+), 1 deletions(-)
diff --git a/src/ut