This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: WSASocketA returns WSAEPROVIDERFAILEDINIT
- To: cygdev <cygwin-developers at cygwin dot com>
- Subject: Re: WSASocketA returns WSAEPROVIDERFAILEDINIT
- From: egor duda <deo at logos-m dot ru>
- Date: Tue, 1 May 2001 17:29:08 +0400
- CC: cygwin-apps at cygwin dot com, Craig Nelson <craig at reversion dot ca>
- Organization: deo
- References: <2415739582.20010430214824@logos-m.ru><20010430215921.M24200@cygbert.vinschen.de>
- Reply-To: egor duda <cygwin-apps at cygwin dot com>
Hi!
Monday, 30 April, 2001 Corinna Vinschen vinschen@redhat.com wrote:
CV> On Mon, Apr 30, 2001 at 09:48:24PM +0400, egor duda wrote:
>> anybody ever seen this?
>>
>> 10733 37491 [main] sh 245 fhandler_socket::fixup_after_fork: WSASocket error
>> 638 38129 [main] sh 245 __set_winsock_errno: fixup_after_fork:168 - winsock error 10106 -> errno 1
CV> Gack! Is that 100% reproducibel or intermittent? What system?
CV> I never saw that before.
pretty reproducible. i've tracked it down. Some component of winsock
wants SystemRoot to be present in environment. patch attached
2001-05-01 Egor Duda <deo@logos-m.ru>
* rshd.c (doit): Pass 'SystemRoot' environment variable to shell.
Without it, some winsock conponents fail to initialize, which leads
to WSAEPROVIDERFAILEDINIT error.
egor. mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19
rshd.diff
rshd.ChangeLog