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
This commit is contained in:
Lennart Poettering 2006-07-14 23:06:44 +00:00
parent fc544a63de
commit b8f9ae00f3

View file

@ -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)); memset(&c->spawn_api, 0, sizeof(c->spawn_api));
c->do_autospawn = 0; c->do_autospawn = 0;
#ifdef SIGPIPE
pa_check_signal_is_blocked(SIGPIPE);
#endif
c->conf = pa_client_conf_new(); c->conf = pa_client_conf_new();
pa_client_conf_load(c->conf, NULL); pa_client_conf_load(c->conf, NULL);
#ifdef HAVE_X11 #ifdef HAVE_X11