From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] sup ignoring SIGTERM?
Date: Wed, 05 Aug 2009 16:35:51 -0400 [thread overview]
Message-ID: <1249504381-sup-8445@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <1249502171-sup-8079@masanjin.net>
Excerpts from William Morgan's message of Wed Aug 05 16:03:09 -0400 2009:
> Good point. I've fixed that in branch ncurses-fixes, which I've merged
> into next. Let me know if it works for you.
I just pulled next and fired it up. It was _hoooooribly_,
_bruuuutallly_ slow to load the index. I git bisected between my
previous running ORIG_HEAD and HEAD. I came up with 75d9f5e3db as the
offender. It seems to do what you intend but (for me, anyway) at the
expense of really bad interactivity. [We're talking 10+ minutes to
load the index part way...]
This doesn't help identify the problem, but I'd be looking at the
Ncurses.nodelay bits...
Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090805/b4062212/attachment.bin>
next prev parent reply other threads:[~2009-08-05 20:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 14:09 Adeodato Simó
2009-08-05 20:03 ` William Morgan
2009-08-05 20:25 ` Nicolas Pouillard
2009-08-05 21:24 ` William Morgan
2009-08-06 17:53 ` William Morgan
2009-08-06 18:09 ` Nicolas Pouillard
2009-08-06 23:56 ` Ben Walton
2009-08-05 20:35 ` Ben Walton [this message]
2009-08-05 21:28 ` Edward Z. Yang
2009-08-06 18:37 ` Adeodato Simó
2009-08-07 1:38 ` William Morgan
2009-08-07 10:31 ` Adeodato Simó
2009-08-07 16:40 ` Rich Lane
2009-08-08 9:23 ` Adeodato Simó
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=1249504381-sup-8445@ntdws12.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
/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