changeset 107545:805495d3c451

Don't call turn_on_atimers around `connect' (Bug#5723).
author YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
date Thu, 25 Mar 2010 17:56:15 +0900
parents afbf4ad814c7
children 59e2de1eaab1 9ffe3226fad6 cc6fa055586c c3622fa53abe
files src/ChangeLog src/process.c
diffstat 2 files changed, 5 insertions(+), 14 deletions(-) [+]
line wrap: on
line diff
--- 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  <mituharu@math.s.chiba-u.ac.jp>
+
+	* process.c (Fmake_network_process): Don't call turn_on_atimers around
+	`connect' (Bug#5723).
+
 2010-03-25  Helmut Eller  <eller.helmut@gmail.com>
 
 	* process.c (Fmake_network_process): Call `select' for interrupted
--- 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.