Mail Archives: cygwin/2001/11/07/09:51:51
I sent a series of mails on this topic at the start of June this year,
with the subject:
inetd under Win95 OSR2.5
I was using Winsock2.
I traced the problem as far as:
A socket is duplicated as stdin. A socket operation is then performed
on stdin, which fails with ENOTSOCK.
The following code demonstrated this:
ns = accept(...)
getpeername(ns, ...) -> Successful, and gets right answer
dup2(ns,0)
getpeername(0, ...) -> Fails with ENOTSOCK
I did not receive any other comments from the mailing list, so I presume
the problem is still there.
Cheers,
Tim
----- Original Message -----
From: "Corinna Vinschen" <cygwin AT cygwin DOT com>
To: <cygwin AT cygwin DOT com>
Sent: Wednesday, November 07, 2001 11:11 AM
Subject: Re: inetd on win95
> Sorry, I neither can find the mails nor any FAQ about that though
> I'm sure I have already written about that problem. Some 95 systems
> have weird problems with their Winsock implementation. And Winsock2
> is not integral part of 95. But you can download a Winsock2 for 95
> at Microsoft:
>
> http://www.microsoft.com/windows95/downloads/contents/wuadmintools/s_wunetworkingtools/w95sockets2/
>
> Please, try this. Hopefully it solves your problem. If not, I can
> only suggest upgrading to XP. 95 is actually _that_ crappy. Even
> upgrading to 98 would be a help.
>
> Or Linux ;-).
>
> Corinna
>
> --
> Corinna Vinschen Please, send mails regarding Cygwin to
> Cygwin Developer mailto:cygwin AT cygwin DOT com
> Red Hat, Inc.
>
> --
> 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/
>
>
--
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 -