Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<FC0B9DA2600ED4118F76009027AA5DDD0485B369@ALEX2>
From:	jeff_burch AT agilent DOT com
To:	cygwin AT cygwin DOT com, cygwin AT cygwin DOT com
Subject:	RE: Problem with accept(2) on the 1003.20.0.0 release
Date:	Fri, 14 Feb 2003 13:09:34 -0800
MIME-Version:	1.0
X-Spam-Status:	No, hits=-97.7 required=5.0
X-Spam-Level:

Cheers to Elfyn!


> Do you by any chance have any firewall software running on the daemon'ish
> machine? ZoneAlaram perhaps?
>
>
> Regards,
>
> Elfyn McBratney
> elfyn AT exposure DOT org DOT uk
> www.exposure.org.uk

I had version 3.21 of Aventail's connect SW installed on the problem machine. I removed it, reinstalled the lastest cygwin, tested!, re-installed version 4.1.2 of Avantail, tested again, and now all is well...

Accept(2) now works as expected with this version of Aventail...

If anyone has a clue as to what was going wrong, I'd love to know. Remember, the problem only occurred with the latest cygwin and this older version of Avantail. The same code compiled with Visual Studio always ran fine. So, there is some interaction between cygwin1.dll and Aventail...

Thanks, Jeff

Jeff Burch
Communications Solutions Department
Agilent Laboratories
Phone: 650-485-6364
Fax:     650-485-8092
email:   jeff_burch AT agilent DOT com



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -