Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <3BEAF733.6000102@sys-mail.net> Date: Thu, 08 Nov 2001 22:20:51 +0100 From: joerg eichhorn User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; de-AT; rv:0.9.4) Gecko/20010913 X-Accept-Language: en-us, de MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: inetd on win95 References: <20011107121139 DOT S2965 AT cygbert DOT vinschen DOT de> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit i have got the same problems, as described in the orginial mail by Raphael. winver: Win9X Ver 4.90 build 73010104 (aut.: it is winme) cygver: Cygwin DLL version info: dll major: 1003 dll minor: 3 dll epoch: 19 build date: Wed Sep 12 23:54:31 EDT 2001 but what i found the following: this won't work: foo AT bar ~ $ /usr/sbin/new/in.telnetd /usr/sbin/new/in.telnetd: getpeername: The descriptor is a file, not a socket foo AT bar ~ $ but the following worked fine: foo AT bar ~ $ /usr/sbin/new/in.telnetd -debug wrapping the call into a shellscript named in.telnetd didn't work :-( so how to understand that behavior? mfg joerg Tim Chick wrote: > 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 -- 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/