Commit bd80a886 authored by YAMAMOTO Mitsuharu's avatar YAMAMOTO Mitsuharu Committed by Chong Yidong

Backport 2010-03-25T08:56:15Z!mituharu@math.s.chiba-u.ac.jp from trunk

parent c2e124a9
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
......
......@@ -3654,23 +3654,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.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment