Mail Archives: cygwin/2001/11/08/16:22:14
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/
- Raw text -