Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <062c01c1679a$440d9590$fa01a8c0@TJC1LAPTOP>
From: "Tim Chick" <tchick AT virata DOT com>
To: <cygwin AT cygwin DOT com>
References: <GMFF7W$I4lMo9pcXo8eU30qeKiy8HkmWwKOkmIm1hbMId1s5Ia0QlJ0 AT voila DOT fr> <20011107121139 DOT S2965 AT cygbert DOT vinschen DOT de>
Subject: Re: inetd on win95
Date: Wed, 7 Nov 2001 14:41:20 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700

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/