GNU bug report logs - #22789
25.1.50; In last master build https connections stop working

Previous Next

Full log

Message #206 received at 22789 <at> debbugs.gnu.org (full text, mbox):

From: Alain Schneble <a.s <at> realize.ch>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: schwab <at> suse.de, larsi <at> gnus.org, j_l_domenech <at> yahoo.com,
 22789 <at> debbugs.gnu.org
Subject: Re: bug#22789: 25.1.50;
 In last master build https connections stop working
Date: Tue, 1 Mar 2016 18:55:11 +0100

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Alain Schneble <a.s <at> realize.ch>
>> CC: <schwab <at> suse.de>, <larsi <at> gnus.org>, <j_l_domenech <at> yahoo.com>,
>> 	<22789 <at> debbugs.gnu.org>
>> Date: Tue, 1 Mar 2016 18:09:40 +0100
>> 
>> Eli Zaretskii <eliz <at> gnu.org> writes:
>> 
>> > So yes, if we have a signal that is delivered from one of these
>> > handshakes, it will cause the loop to run again.
>> 
>> I guess if we do a fcntl(socket, F_SETFL, O_ASYNC), we may get a
>> notification if the socket has been connected.
>
> Doesn't the socket become read-ready in 'pselect' once it is
> connected?

True, that may indeed be the case (or write-ready?  I'm confused ;( ).

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.