Re: [Evolution] IMAP scanning gets stuck

[Jeffrey Stedfast <fejj ximian com>]

On Fri, 2001-11-23 at 17:31, Dan Winship wrote:
> On Fri, 2001-11-23 at 19:03, Jeffrey Stedfast wrote:
> > I wish there was a way to manually set the tcp timeout, but there isn't.
>
> We could do a non-blocking connect followed by a select with a timeout.
>
> However, the tcp timeout isn't 30 minutes anyway, so something else is
> going on here.

Yea, 30 minutes does seem to be a bit high... but I just assumed he was
exaggerating.

from the manpage:

       ETIMEDOUT
              Timeout while attempting connection. The server may
              be  too  busy  to accept new connections. Note that
              for IP sockets the timeout may be  very  long  when
              syncookies are enabled on the server.

so maybe the server has syncookies enabled? they don't really say what
"very long" is :-)

Anyways, we already set the socket to O_NONBLOCK before we connect() and
do a select() on the socket after afaik, so this doesn't seem to work on
linux systems.

Also, I seem to recall reading in some man page or another that the
linux connect() always blocks anyway? I could have sworn I read this a
while back after noticing that winsock was able to do non-blocking
connect()'s.


ah, I was right...we *do* use O_NONBLOCK on the socket while
connect()ing... we also set the timeout to 4 minutes (which is the
standard tcp timeout for blocking connects) while also allowing the user
to cancel the connection with the stop button.

I guess we could set the timeout to something smaller, but I don't see
what that really gains us here (since the user can force a disconnect at
any time).

Jeff

> -- Dan
>
> _______________________________________________
> evolution maillist  -  evolution ximian com
> http://lists.ximian.com/mailman/listinfo/evolution