This is the mail archive of the
cygwin-developers@sources.redhat.com
mailing list for the Cygwin project.
Re: Any better now?
- To: Chris Faylor <cgf at cygnus dot com>, cygwin-developers at sources dot redhat dot com
- Subject: Re: Any better now?
- From: Corinna Vinschen <vinschen at cygnus dot com>
- Date: Thu, 24 Aug 2000 15:30:57 +0200
- References: <20000824000822.A10979@cygnus.com> <39A5206F.15DD74F8@cygnus.com>
- Reply-To: cygdev <cygwin-developers at sources dot redhat dot com>
Corinna Vinschen wrote:
>
> Chris Faylor wrote:
> >
> > I've checked in some patches to cygwin which fix inetd/telnet operation
> > for me. Do they work for you, Corinna? I haven't tried sshd yet.
BTW: You can't compare inetd/sshd operations since inetd uses
service manager operations. The inetd child isn't a real child
process but a thread which is forked by the service manager.
However, inetd operations aren't working correctly, too:
- Starting inetd by `net start inetd':
Ok
- Starting telnet session (fork/execs in.telnetd -> fork/execs login):
Ok
- login exec's tcsh while in.telnetd manages communication:
Ok.
- Ctrl-D exits tcsh:
Ok.
- Exiting tcsh causes exiting in.telnetd:
Nope, in.telnetd remains in memory, wasting 100% CPU.
- `net stop inetd' stops inetd:
Nope. It crashes with access violation.
Corinna