Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 8 Aug 2002 13:53:35 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: OpenSSH and WinCVS in Windows 9x Message-ID: <20020808175335.GG11425@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20020806140534 DOT 757a155a DOT steven DOT obrien2 AT ntlworld DOT com> <200208081356 DOT 37427 DOT laurent DOT pinchart AT capflow DOT com> <168935202570 DOT 20020808161859 AT logos-m DOT ru> <200208081932 DOT 25737 DOT laurent DOT pinchart AT capflow DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200208081932.25737.laurent.pinchart@capflow.com> User-Agent: Mutt/1.3.23.1i On Thu, Aug 08, 2002 at 07:32:25PM +0200, Laurent Pinchart wrote: >It seems that the problem isn't in WinCVS nor in ssh but in the cygwin select >implementation. The problem is not in cygwin. If you are communicating with pipes between non-cygwin application and a cygwin application and expecting EOF notification on pipes you are not going to get it. Microsoft doesn't provide any reliable way of finding that information on Windows 9x. Btw, asking for no bytes in PeekNamedPipe is perfectly legal according MSDN. I doubt that would actually fix the problem but you or Egor are welcome to make that change and see if it solves the problem. 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/