delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
From: | "Brian Kelly" <brian DOT m DOT kelly AT verizon DOT net> |
To: | <cygwin AT cygwin DOT com> |
Subject: | RE: Cygwin deadlocks due to broken select() when writing to pipes |
Date: | Thu, 30 Oct 2003 23:14:36 -0500 |
Message-ID: | <005901c39f65$7f7875a0$6700a8c0@maxstars8g31h2> |
MIME-Version: | 1.0 |
X-Priority: | 3 (Normal) |
X-MSMail-Priority: | Normal |
X-MimeOLE: | Produced By Microsoft MimeOLE V6.00.2600.0000 |
In-Reply-To: | <20031031033119.611A4E55A@carnage.curl.com> |
Importance: | Normal |
X-Authentication-Info: | Submitted using SMTP AUTH at out007.verizon.net from [141.153.207.175] at Thu, 30 Oct 2003 22:14:35 -0600 |
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. My biggest headache is - occasional DEADLOCKS. About once or twice a day a bash process attempting to start an ftp instance will hang - and freeze everything clear up to the perl parent process that launched it. Perl itself even hangs and stops writing output to log files and the terminal. The deadlock situation will last indefinitely until I do a kill -9 and terminate the last bash shell launched by the perl script. Then, every other process associated with the parent perl script "comes back to life". I am not a c/c++ programmer. My expertise is in Perl - and there it shall remain. I spent a couple hours a few weeks ago trying to incorporate strace into the mix I run, but it turned out to be a really complicated undertaking - so I gave up on it. So I apologize for effectively offering nothing more than a BIG "me too!!". That said ..... ME TOO!!! Brian Kelly -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |