This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: OpenSSL problem ? (Was Re: Pine 4.58 for Cygwin takes a verylong time to close a certain IMAP INBOX)


On Wed, 12 Nov 2003, Corinna Vinschen wrote:

> On Wed, Nov 12, 2003 at 04:15:46PM -0200, Fr?d?ric L. W. Meunier wrote:
> > On Wed, 12 Nov 2003, Brian Ford wrote:
> >
> > > Corinna,
> > >
> > > Did you get a chance to look at the strace output he posted here:
> > >
> > > http://pervalidus.port5.com/tmp/imap.txt.gz
> > >
> > > A glance there by trained eyes might save him some time.  I don't have the
> > > time or the training for mine :).  It appears to be stuck in close on the
> > > socket after is has shutdown?
> >
> > It seems to be cause by the firewall from my SpeedStream 5200.
> >
> > 'a logout' worked once I disabled filtering 'TCP NULL', but the
> > Pine delays remain.
> >
> > Anyway, why it worked on plain Windows and Linux is another
> > story. I don't have any other firewalls enabled.
>
> fhandler_socket::close() tries to circumvent problems with unexpected
> data loss which can occur, if an application exits without having
> waited for the closesocket() call being successful.  The problem with
> the latter is, that there's no way to find out.  Therefore Cygwin
> lingers on closesocket(), even with non-blocking sockets.  I don't
> know if that helps but you could try to build a Cygwin DLL which only
> lingers if shutdown hasn't been called.  I tried it with ssh and it
> seems at least not to disturb ssh operation.  Patch below.

It behaves the same. I applied your patch and compiled latest
CVS.

6735077 Nov 12 17:02 cygwin1.dll

And in gdb I still see

#2  0x00000005 in ?? ()
#3  0x00000004 in ?? ()
#4  0x00000001 in ?? ()
#5  0x00e3ffd0 in ?? ()
#6  0x81f2eda8 in ?? ()
#7  0xffffffff in ?? ()

Anyway, since disabling filtering 'TCP NULL' worked for 'a
logout' I'll see what I can do in the modem configuration to
make the Pine delays go away. Disabling all ADS (Attack
Detection System), which has:

Same Source and Destination Address
Broadcast Source Address
LAN Source Address On WAN
Invalid IP Packet Fragment
TCP NULL
TCP FIN
TCP Xmas
Fragmented TCP Packet
Fragmented TCP Header
Fragmented UDP Header
Fragmented ICMP Header
Inconsistent UDP/IP header lengths
Inconsistent IP header lengths

didn't help.

-- 
How to contact me - http://www.pervalidus.net/contact.html

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]