Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Thu, 24 Aug 2000 12:13:47 -0400 From: Chris Faylor To: cygdev Subject: Re: Any better now? Message-ID: <20000824121347.E12911@cygnus.com> Reply-To: cygwin-developers AT sources DOT redhat DOT com Mail-Followup-To: cygdev References: <20000824000822 DOT A10979 AT cygnus DOT com> <39A5206F DOT 15DD74F8 AT cygnus DOT com> <39A52391 DOT C958ECD5 AT cygnus DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <39A52391.C958ECD5@cygnus.com>; from vinschen@cygnus.com on Thu, Aug 24, 2000 at 03:30:57PM +0200 On Thu, Aug 24, 2000 at 03:30:57PM +0200, Corinna Vinschen wrote: >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. I don't see this. in.telnetd goes away. >- `net stop inetd' stops inetd: > Nope. It crashes with access violation. Nor this. inetd exits normally. Could you send me your DLL? cgf