WSASocketA returns WSAEPROVIDERFAILEDINIT

[egor duda]

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

-------------- next part --------------
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rshd.diff
Type: text/x-diff
Size: 645 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin-developers/attachments/20010501/f8553a35/attachment.bin>