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 From: "Hannu E K Nevalainen" To: "ML CygWIN" Cc: "Mark Thornton" Subject: RE: rsync local dir copy hang - solved for me Date: Fri, 24 Oct 2003 16:04:42 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-reply-to: <3F98FB3C.3050502@ntlworld.com> Importance: Normal > From: Mark Thornton > Sent: Friday, October 24, 2003 12:13 PM Mark, please - even if your repliy might seem a bit personal - do keep replies on the list. There might be some little spark, that makes others have a fire lit (i.e. get a bright idea). > >The bottom point: *don't do that* ;-) > > i.e. leave the msleep() call there. This is a simple - yet > effective - way > >to avoid ill effects of a tight loop. > > > > > > However it remains true that there is some sort of bug in rsync's thread > handling (or perhaps in cygwin's thread library). Hmmm... I think I read something about a similiar thing, having the word "pthreads" in the subject. Might this be related? > For some a cure for > this, even using busy waiting, may be preferable to the bug. > > Mark Thornton For the time beeing, yes it might be preferable - but not as a long time solution. And one has to be aware of the possible ill effects. /Hannu E K Nevalainen, B.Sc. EE - 59?16.37'N, 17?12.60'E -- printf("Timezone: %s\n", (DST)?"UTC+02":"UTC+01"); -- --END OF MESSAGE-- -- 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/