This is the mail archive of the
mailing list for the Cygwin project.
Re: cygwin deadlocks due to broken select() when writing to pipes
- From: "Dylan Cuthbert" <dylan at q-games dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 3 Nov 2003 00:29:53 +0900
- Subject: Re: cygwin deadlocks due to broken select() when writing to pipes
- References: <20031031033119.611A4E55A@carnage.curl.com> <firstname.lastname@example.org> <20031031042355.GA23231@redhat.com>
Actually I think I did mention I was running rsync hourly in a cron job,
that's all I've been mentioning as far as I know.
But anyway, this is 100% repeatable on my machine over the course of a day;
try setting up a cronjob to run every hour that rsync's a gig or so of files
over the intranet somewhere. Over the course of the day 1 in 4 of those
cronjobs will still be hanging around doing nothing (cpu usage 0).
The problem I have is that, since the Sep. 19th(?) version, when I log out
or shutdown WinXP, these idling tasks are no longer forcibly killed (because
they are idling deep in cygwin's lib code I suspect), but they used to be
killed just fine with the version of cygwin before the 19th.
Anyway, Right now I am resolved to having to leave my machine shutting down
for hours on end each night :-( not a good solution really especially as I
pay the electricity bills around here... )
Q-Games, Dylan Cuthbert.
"Christopher Faylor" <email@example.com> wrote in
> On Fri, Oct 31, 2003 at 12:44:54PM +0900, Dylan Cuthbert wrote:
> >This could explain my problems running rsync as a cronjob
> I don't remember you mentioning that you were sending large amounts of
> data over a pipe before.
> The only time this is a problem is when the pipe is full.
> And, yes, it is a known problem.
> I would have expected that someone would have offered a patch for the
> documentation by now. I don't know why they haven't done that.
> Please use the resources at cygwin.com rather than sending personal email.
> Special for spam email harvesters: send email to firstname.lastname@example.org
> and be permanently blocked from mailing lists at sources.redhat.com
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html