Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 30 Oct 2003 23:23:55 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygwin deadlocks due to broken select() when writing to pipes Message-ID: <20031031042355.GA23231@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20031031033119.611A4E55A@carnage.curl.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Note-from-DJ: This may be spam On Fri, Oct 31, 2003 at 12:44:54PM +0900, Dylan Cuthbert wrote: >This could explain my problems running rsync as a cronjob I don't remember you mentioning that you were sending large amounts of data over a pipe before. The only time this is a problem is when the pipe is full. And, yes, it is a known problem. I would have expected that someone would have offered a patch for the documentation by now. I don't know why they haven't done that. -- Please use the resources at cygwin.com rather than sending personal email. Special for spam email harvesters: send email to aaaspam@sourceware.org and be permanently blocked from mailing lists at sources.redhat.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/