From: garoth@gmail.com (Andrei Thorp)
Subject: [sup-talk] Sup locking up
Date: Thu, 11 Jun 2009 13:58:26 -0400 [thread overview]
Message-ID: <80055d7c0906111058q128b5eb7na8931a8b75b0d0bf@mail.gmail.com> (raw)
In-Reply-To: <1244735117-sup-6933@ntdws12.chass.utoronto.ca>
Yeah...
I have a theory. Have you learned some new stuff about screen lately?
Screen has this binding that pretty much makes it freeze up. I guess
I'm talking about http://savannah.gnu.org/bugs/?11610 which applies to
screen 4.0.0, which is the one people have.
Try maybe running sup out of screen for a while and see if it can happen then.
Another test: if screen locks up but sup respects regular kill (not
-9), sup's not locked up itself.
-AT
next prev parent reply other threads:[~2009-06-11 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 9:05 Marcus Williams
2009-06-11 11:23 ` Ben Walton
2009-06-11 14:23 ` Marcus Williams
2009-06-11 15:46 ` Ben Walton
2009-06-11 17:58 ` Andrei Thorp [this message]
2009-06-11 19:09 ` Marcus Williams
2009-06-12 4:38 ` Edward Z. Yang
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=80055d7c0906111058q128b5eb7na8931a8b75b0d0bf@mail.gmail.com \
--to=garoth@gmail.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