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: <3BEB1ACE.5080008@sys-mail.net>
Date: Fri, 09 Nov 2001 00:52:46 +0100
From: joerg eichhorn <joerg DOT eichhorn AT sys-mail DOT net>
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: <GMFF7W$I4lMo9pcXo8eU30qeKiy8HkmWwKOkmIm1hbMId1s5Ia0QlJ0 AT voila DOT fr> <20011107121139 DOT S2965 AT cygbert DOT vinschen DOT de> <3BEAF733 DOT 6000102 AT sys-mail DOT net> <20011108165027 DOT B4977 AT redhat DOT com> <3BEB02AC DOT 40503 AT sys-mail DOT net> <20011108175253 DOT A5473 AT redhat DOT com>
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 7bit

thank you for your time.

i havn't the knowledge nor the will to inspect the source code...
i simply wanted to run div. net-services, but have not the ability to 
debug it, faq and user guide did were no help. so i thought you could 
give me some hints, how to get further.

i've installed cygwin (vers. infos i prov.d erlier), started iu-config.
after that standard services in /etc/inetd.conf should work.
so i have tried:
$ /usr/sbin/inetd
as described in /usr/doc/Cygwin/inetutils-1.3.2.README. ps showed me 
that inetd was running. so i've tried to connect from other machine:
$ telnet 10.0.0.4
Trying 10.0.0.4...
Connected to 10.0.0.4.
Escape character is '^]'.

after "Escape character is '^]'." nothing went further (i think login 
should appear at this point) those where the things, described in the 
original mail by raphael.

when i saw, that this was not working, i tested:
$ /usr/sbin/inetd -d
produced output:
some lines of ADD: ... \n registered on n
looked good to me.
when tried to connect again:
someone wants telnet
accept, ctrl 3
+ Closing from 21
353653 execl /usr/sbin/in.telnetd

and nothing more, same behavior as before. so i looked into 
/etc/inetd.conf, found out that inetd calls /usr/sbin/in.telnetd, so i 
thought: try to start it directly from cmdline (as also described in 
manpage):
$ /usr/sbin/in.telnetd.exe -debug
and found out, that the connecting was established. i was wondering, but 
you already were telling my the reason. because to me it doesnt has to 
be perfect it's enough, if its working, i've tried:
$ mv /usr/sbin/in.telnetd.exe /usr/sbin/in.telnetd_dist.exe
and created /usr/sbin/in.telnet with the following content:
#!/bin/bash
/usr/sbin/in.telnetd_dist.exe -debug

i thougt to inetd it seems to be the same and telnetd gets debugmode as 
he likes it. but: when starting my script from cmdline, it works, but it 
won't when called from inetd.

can you give me some hints, how to get further?
i think, i have winsock2, and i dont want to install any other os.

thank you for your time, good night
gruss joerg eichhorn


Christopher Faylor wrote:

> On Thu, Nov 08, 2001 at 11:09:48PM +0100, joerg eichhorn wrote:
> 
>>why did the shellwrap not work?
>>
> 
> Hard to say since the only details you provided were:
> 
> 
>>wrapping the call into a shellscript named in.telnetd didn't work :-(
>>so how to understand that behavior?
>>
> 
> It's difficult to understand what you were hoping to accomplish by
> wrapping in.telnetd in a shell script.  If you were attempting to run
> the shell script under inetd then that really is not going to do the
> right thing.  in.telnetd is supposed to work without this.  Adding
> -debug to a program that is being run by inetd is not the way to
> solve the problem.
> 
> I will point out that what we are hoping for when we ask people to
> debug a problem is not YA "I doesn't work for me, either!" or experimenting
> with tools to see what previously unheard of options might do for you.
> 
> Debugging for this situation would be something like:  "It works for
> Windows 95 when I've installed the Alfalfa 1.13 FTP client.  I noticed that
> if I was using the Spanky 5.27 net browser that it would stop working.
> Inspecting the files that are released along with these programs, I
> can see that both contain versions of the petey32.dll."
> 
> Or, even better inspect the source code and compare and contrast what
> was done in a release that (theoretically) worked -- at the source
> code level.
> 
> cgf
> 
> --
> 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/