Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Mon, 11 Dec 2000 13:36:05 -0500 From: Christopher Faylor To: cygwin Subject: Re: Why does scp leave ssh running? -- select() never returns Message-ID: <20001211133605.B7497@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin References: <3A22C383.5C16BBC8@delcomsys.com> <3A25C7DA.6F76C8DA@delcomsys.com> <20001129224015.B21867@redhat.com> <3A266130.F5877EB5@delcomsys.com> <3A271DCD.99BDDBF5@delcomsys.com> <20001202200832.A18661@redhat.com> <3A29C260.1C491A30@delcomsys.com> <20001202233944.A19867@redhat.com> <3A2A16B5.E1C3F9F4@redhat.com> <3A351ADE.EF54C845@delcomsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3A351ADE.EF54C845@delcomsys.com>; from wpd@delcomsys.com on Mon, Dec 11, 2000 at 01:20:14PM -0500 On Mon, Dec 11, 2000 at 01:20:14PM -0500, Patrick Doyle wrote: >So far, the most elegant solution I have come up with is to reimplement >'select()' so that it calls 'ReadFileEx()' with a suitable 'OVERLAPPED' >structure, thus eliminating the separate thread that wakes up every 10 >ms. Of course, if I read a byte from the pipe, I would have to buffer >it somewhere and fix 'read()' so that it checks for the "readahead" byte >first, but that is basically solvable. If the call to 'select()' >returned for some other reason (i.e. another fd was made ready), then >call 'CancelIo()' to terminate the asynchronous read. I'm pretty sure that overlapped I/O does not work with any flavor of pipe. It should be possible to make a simple test case, to verify though. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com