From b8f9ae00f341c936eb27dd51d307f99682a09685 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Fri, 14 Jul 2006 23:06:44 +0000 Subject: remove checking for SIGPIPE blocking from client code. Because we use send(,,MSG_NOSIGNAL) for most socket writes now the reason for SIGPIPE blocking is no longer give. We keep this check for the server side however, because pipes create SIGPIPE too but cannot be used with MSG_NOSIGNAL. Some modules use pipes for internal and external communication. git-svn-id: file:///home/lennart/svn/public/pulseaudio/trunk@1086 fefdeb5f-60dc-0310-8127-8f9354f1896f --- src/pulse/context.c | 4 ---- 1 file changed, 4 deletions(-) diff --git a/src/pulse/context.c b/src/pulse/context.c index 648024c3..5724765b 100644 --- a/src/pulse/context.c +++ b/src/pulse/context.c @@ -132,10 +132,6 @@ pa_context *pa_context_new(pa_mainloop_api *mainloop, const char *name) { memset(&c->spawn_api, 0, sizeof(c->spawn_api)); c->do_autospawn = 0; -#ifdef SIGPIPE - pa_check_signal_is_blocked(SIGPIPE); -#endif - c->conf = pa_client_conf_new(); pa_client_conf_load(c->conf, NULL); #ifdef HAVE_X11 -- cgit