From 46a3726a58efc0517b44be7bc572943bd44f7e2e Mon Sep 17 00:00:00 2001 From: David Henningsson Date: Fri, 5 Apr 2013 16:48:21 +0200 Subject: socket-server: Make the new channel low-delay, not the listening one I don't know if it matters a lot, but most certainly it must be the new channel that's supposed to be made low-delay, not the existing listening socket, right? Signed-off-by: David Henningsson --- src/pulsecore/socket-server.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/pulsecore/socket-server.c b/src/pulsecore/socket-server.c index 0b0b2a5c..74db9e32 100644 --- a/src/pulsecore/socket-server.c +++ b/src/pulsecore/socket-server.c @@ -133,9 +133,9 @@ static void callback(pa_mainloop_api *mainloop, pa_io_event *e, int fd, pa_io_ev /* There should be a check for socket type here */ if (s->type == SOCKET_SERVER_IPV4) - pa_make_tcp_socket_low_delay(fd); + pa_make_tcp_socket_low_delay(nfd); else - pa_make_socket_low_delay(fd); + pa_make_socket_low_delay(nfd); pa_assert_se(io = pa_iochannel_new(s->mainloop, nfd, nfd)); s->on_connection(s, io, s->userdata); -- cgit v1.2.3