RE: cygwin deadlocks due to broken select() when writing to pipes

["Brian Kelly" <brian dot m dot kelly at verizon dot net>]

> 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!"

So "this *probably* is it" would make you feel better? ( No I didn't
think so either ). Assuming you're *human* cgf ;-), you're *interest* in
hunting down any particular intermittent and well hidden bug would be in
pretty close relation to the number of folks experiencing it as a
problem - however "nebulously". Squeaky wheel gets the grease - squeaky
wheel*s* get a factory recall. It's pretty obvious that the number of
"me too's" are sufficient only to *irritate* - not *interest* you - at
this point. Nevertheless, a few persistent reminders over a long period
can have the same effect as a very large number of complaints in close
proximity. There was once a great story in the Reader's Digest I think
of some prisoner somewhere who decided that it'd be nice to have a new
library in the prison. So he started writing lawmakers and telling them
that he wanted a new library for the prison. Every day he mailed a
couple of dozen hand written letters. For three of four years they were
ignored. Then eventually he started getting VERY nasty responses telling
him to bug off. Some even called the warden to get him to stop, but
civil libertarians soon took interest in this and threatened to sue on
his behalf if his mail was censured. Finally everyone was eventually
worn down and around year ten, the legislature voted to fund the
construction of his library - allocating close to TWO MILLION DOLLARS
for the effort.

As for your *mean* response serving as a deterrent - your ongoing rant
about not wanting to hear from non-contributors is just that - ongoing
.......

Brian Kelly


-----Original Message-----
From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On Behalf
Of Christopher Faylor
Sent: Thursday, October 30, 2003 11:36 PM
To: cygwin@cygwin.com
Subject: Re: cygwin deadlocks due to broken select() when writing to
pipes

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/


--
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/