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, 30 Oct 2003 23:35:53 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygwin deadlocks due to broken select() when writing to pipes Message-ID: <20031031043553.GB23231@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20031031033119 DOT 611A4E55A AT carnage DOT curl DOT com> <005901c39f65$7f7875a0$6700a8c0 AT maxstars8g31h2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <005901c39f65$7f7875a0$6700a8c0@maxstars8g31h2> User-Agent: Mutt/1.4.1i On Thu, Oct 30, 2003 at 11:14:36PM -0500, Brian Kelly wrote: >Thank you Bob Byrnes for this info and analysis. Perhaps it will >result in a solution to a long simmering problem. I use cygwin VERY >aggressively. A cron job launches a 20,000 line perl script (not >including CPAN modules by other authors) that does complex network >automation tasks via multiple chained telnets and ftps. (Eventually to >use ssh). Cron launches this script every five minutes and multiple >instances share resources managed by semaphores. cgf wasn't even >remotely in the mood for endorsing cygwin for this kind of 'abuse' (not >his exact words). Nevertheless, for "the most part" it works >extraordinarily well. So, predictably, we will now be seeing everyone who has ever seen a hang anywhere near cygwin chiming in with a "THIS MUST BE IT!" I am always interested in fixing bugs in cygwin but bugs like of "I run it for a real long time and something bad happens. I'm not a programmer and have no idea how to provide any useful feedback" are onex I steer clear of. Perhaps this mean response will serve as a deterrent for anyone (except possibly one of my "groupies" who occasional pop up to comment on my character flaws and then disappear) from responding unless there is real useful data to provide? >I am not a c/c++ programmer. My expertise is in Perl - and there it >shall remain. If that is the case, then why are you presuming that the described problem has anything to do with you? You have admitted that you couldn't possibly know if the programs that you are using are performing a select on a pipe since you don't know c or c++. cgf -- 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/