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 X-Injected-Via-Gmane: http://gmane.org/ To: cygwin@cygwin.com From: "Dylan Cuthbert" Subject: Re: cygwin deadlocks due to broken select() when writing to pipes Date: Mon, 3 Nov 2003 11:54:54 +0900 Lines: 40 Message-ID: References: <20031031033119.611A4E55A@carnage.curl.com> <20031031042355.GA23231@redhat.com> <20031102194147.GA15320@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 CYGWIN=tty is on in the system env vars, shall I switch it off, is this bad? I switched it on before I had this problem mind you, but maybe something in the post-Sept-19th version mixes badly with CYGWIN=tty? Yes, I understand the "root of the problem" problem (sic.), ie. the programming law that there will always be a lot more causes than there are distinct effects. ;-) Anyway, I have this daily recurring problem, which seems to me to be duplicatible, yet no-one has tried to duplicate it yet? This is why I repeat the description of my problem wherever I can; in the daft hope someone will set up something similar and see if they get the same thing. I'm not doing anything complicated, just 2 or 3 rsync's (of half a gig or so) in a cronjob every two hours to a linux server. Regards --------------------------------- Q-Games, Dylan Cuthbert. http://www.q-games.com "Christopher Faylor" wrote in message news:20031102194147.GA15320@redhat.com... > 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/