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:	<3BEB00D9.4090607@cportcorp.com>
Date:	Thu, 08 Nov 2001 17:02:01 -0500
From:	Peter Buckley <peter DOT buckley AT cportcorp DOT com>
User-Agent:	Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language:	en-us
MIME-Version:	1.0
To:	joerg eichhorn <joerg DOT eichhorn AT sys-mail DOT net>
CC:	cygwin AT cygwin DOT com
Subject:	Re: inetd on win95
References:	<GMFF7W$I4lMo9pcXo8eU30qeKiy8HkmWwKOkmIm1hbMId1s5Ia0QlJ0 AT voila DOT fr> <20011107121139 DOT S2965 AT cygbert DOT vinschen DOT de> <3BEAF733 DOT 6000102 AT sys-mail DOT net>

This should NOT work, by design. You need to run inetd,
and it will by default startup the telnet daemon. You
can edit your inetd.conf file to pick and choose whether
you run telnet, ftp, rsh, rlogin. By default, inetd
starts all of these.

HTH,
Peter

joerg eichhorn wrote:

> 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:
> <snip>
> 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 ~
> $
> </snip>
> 
> but the following worked fine:
> <snip>
> foo AT bar ~
> $ /usr/sbin/new/in.telnetd -debug
> 
> </snip>
> 
> 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/
> 


-- 
Your mouse has moved.
Windows NT must be restarted for the change to take effect.
Reboot now?  [OK]

--


--
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 -