From: "Dylan Cuthbert" <dylan@q-games.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin deadlocks due to broken select() when writing to pipes
Date: Fri, 31 Oct 2003 05:14:00 -0000 [thread overview]
Message-ID: <bnslrn$l6f$1@sea.gmane.org> (raw)
In-Reply-To: <20031031033119.611A4E55A@carnage.curl.com>
This could explain my problems running rsync as a cronjob and having the
tasks hang for long periods of time (they do terminate eventually). Its a
real pain when I try and log out or shutdown, as windows can't seem to
forcibly terminate the tasks (because they are spawned by a SYSTEM task -
the cron daemon - I suppose) and so just sits there for 30 minutes to an
hour trying to shutdown or log off. I can't even ctrl-alt-del to bring up
the task manager because I presume windows has gone into some internal
system time-out loop of some kind.
---------------------------------
Q-Games, Dylan Cuthbert.
http://www.q-games.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/
next prev parent reply other threads:[~2003-10-31 3:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-31 4:35 Bob Byrnes
2003-10-31 5:14 ` Dylan Cuthbert [this message]
2003-10-31 5:27 ` cygwin " Christopher Faylor
2003-11-02 15:29 ` Dylan Cuthbert
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='bnslrn$l6f$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).