public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Dylan Cuthbert" <dylan@q-games.com>
To: cygwin@cygwin.com
Subject: Re: cygwin deadlocks due to broken select() when writing to pipes
Date: Sun, 02 Nov 2003 15:29:00 -0000	[thread overview]
Message-ID: <bo37tj$855$1@sea.gmane.org> (raw)
In-Reply-To: <20031031042355.GA23231@redhat.com>

Hi Chris,

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... )

Regards

---------------------------------
Q-Games, Dylan Cuthbert.
http://www.q-games.com

"Christopher Faylor" <cgf-no-personal-reply-please@cygwin.com> wrote in
message news:20031031042355.GA23231@redhat.com...
> 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 aaaspam@sourceware.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
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2003-11-02 15:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-31  4:35 Cygwin " Bob Byrnes
2003-10-31  5:14 ` Dylan Cuthbert
2003-10-31  5:27   ` cygwin " Christopher Faylor
2003-11-02 15:29     ` Dylan Cuthbert [this message]
2003-11-02 19:41       ` Christopher Faylor
2003-11-03  2:55         ` Dylan Cuthbert
2003-11-05  1:52           ` Dylan Cuthbert
2003-11-12  2:29             ` Dylan Cuthbert
2003-11-12 17:45               ` Brian Ford
2003-10-31  5:22 ` Cygwin " Brian Kelly
2003-10-31  5:55   ` cygwin " Christopher Faylor
2003-10-31  9:02     ` Brian Kelly
2003-10-31  9:15       ` Christopher Faylor
2003-10-31 14:09         ` cygwin deadlocks due to lack of money Brian Kelly
2003-10-31 16:12           ` Christopher Faylor
2003-11-01  6:07         ` cygwin deadlocks due to broken select() when writing to pipes Brian Kelly

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='bo37tj$855$1@sea.gmane.org' \
    --to=dylan@q-games.com \
    --cc=cygwin@cygwin.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).