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: Sun, 2 Nov 2003 14:41:47 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygwin deadlocks due to broken select() when writing to pipes Message-ID: <20031102194147.GA15320@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20031031033119.611A4E55A@carnage.curl.com> <20031031042355.GA23231@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Mon, Nov 03, 2003 at 12:29:53AM +0900, Dylan Cuthbert wrote: >Actually I think I did mention I was running rsync hourly in a cron job, >that's all I've been mentioning as far as I know. Which has nothing to do with selecting on pipes unless (and even this is pretty remote) you have turned on CYGWIN=tty for your cron for some reason. The point that I am vainly trying to make is that if one person reports a symptom like "hanging" and another person reports a symptom like "hanging" in a completely different scenario while offering a rationale for the behavior, it does not automatically mean that person B has found the root cause for person A's problem unless person A and person B's situations are the same. There is nothing in your (repeated) description of your problem to indicate that is the case. -- 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/