From: "Hannu E K Nevalainen" <garbage_collector@telia.com>
To: "ML CygWIN" <cygwin@cygwin.com>
Cc: "Mark Thornton" <mark.p.thornton@ntlworld.com>
Subject: RE: rsync local dir copy hang - solved for me
Date: Fri, 24 Oct 2003 15:25:00 -0000 [thread overview]
Message-ID: <NGBBLLIAMFLGJEOAJCCEIELODFAA.garbage_collector@telia.com> (raw)
In-Reply-To: <3F98FB3C.3050502@ntlworld.com>
> 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/
next parent reply other threads:[~2003-10-24 14:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F98FB3C.3050502@ntlworld.com>
2003-10-24 15:25 ` Hannu E K Nevalainen [this message]
2003-10-24 15:41 Bakken, Luke
2003-10-25 14:49 ` Corinna Vinschen
2003-10-25 16:08 ` Hannu E K Nevalainen
2003-10-28 15:08 ` Mark Paulus
-- strict thread matches above, loose matches on Subject: below --
2003-10-24 3:57 Bakken, Luke
2003-10-24 4:18 ` Peter J. Stieber
2003-10-24 4:46 ` Larry Hall
2003-10-24 12:29 ` Hannu E K Nevalainen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=NGBBLLIAMFLGJEOAJCCEIELODFAA.garbage_collector@telia.com \
--to=garbage_collector@telia.com \
--cc=cygwin@cygwin.com \
--cc=mark.p.thornton@ntlworld.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).