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 Message-ID: <39A52391.C958ECD5@cygnus.com> Date: Thu, 24 Aug 2000 15:30:57 +0200 From: Corinna Vinschen Reply-To: cygdev X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.14-SMP i686) X-Accept-Language: de, en MIME-Version: 1.0 To: Chris Faylor , cygwin-developers AT sources DOT redhat DOT com Subject: Re: Any better now? References: <20000824000822 DOT A10979 AT cygnus DOT com> <39A5206F DOT 15DD74F8 AT cygnus DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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