From cad4261fd31b3dec552ffc4dfd66c0b2a19169ce Mon Sep 17 00:00:00 2001
From: YAMAMOTO Mitsuharu
Date: Thu, 25 Mar 2010 17:56:15 +0900
Subject: Don't call turn_on_atimers around `connect' (Bug#5723).

---
 src/process.c | 14 --------------
 1 file changed, 14 deletions(-)

(limited to 'src/process.c')

diff --git a/src/process.c b/src/process.c
index 789befc2a6b..268a3ad7bab 100644
--- a/src/process.c
+++ b/src/process.c
@@ -3615,23 +3615,9 @@ usage: (make-network-process &rest ARGS)  */)
       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.
-- 
cgit v1.2.1