# HG changeset patch # User YAMAMOTO Mitsuharu # Date 1269507375 -32400 # Node ID 805495d3c4512dad7fac87e774894690ddf6fc43 # Parent afbf4ad814c7656a0bab3cb6bb0b8e8288a47cc4 Don't call turn_on_atimers around `connect' (Bug#5723). diff -r afbf4ad814c7 -r 805495d3c451 src/ChangeLog --- a/src/ChangeLog Thu Mar 25 17:48:52 2010 +0900 +++ b/src/ChangeLog Thu Mar 25 17:56:15 2010 +0900 @@ -1,3 +1,8 @@ +2010-03-25 YAMAMOTO Mitsuharu + + * process.c (Fmake_network_process): Don't call turn_on_atimers around + `connect' (Bug#5723). + 2010-03-25 Helmut Eller * process.c (Fmake_network_process): Call `select' for interrupted diff -r afbf4ad814c7 -r 805495d3c451 src/process.c --- a/src/process.c Thu Mar 25 17:48:52 2010 +0900 +++ b/src/process.c Thu Mar 25 17:56:15 2010 +0900 @@ -3615,23 +3615,9 @@ immediate_quit = 1; QUIT; - /* This turns off all alarm-based interrupts; the - bind_polling_period call above doesn't always turn all the - short-interval ones off, especially if interrupt_input is - set. - - It'd be nice to be able to control the connect timeout - though. Would non-blocking connect calls be portable? - - This used to be conditioned by HAVE_GETADDRINFO. Why? */ - - turn_on_atimers (0); - ret = connect (s, lres->ai_addr, lres->ai_addrlen); xerrno = errno; - turn_on_atimers (1); - if (ret == 0 || xerrno == EISCONN) { /* The unwind-protect will be discarded afterwards.