From: ezyang@MIT.EDU (Edward Z. Yang)
Subject: [sup-talk] Sup locking up
Date: Fri, 12 Jun 2009 00:38:42 -0400 [thread overview]
Message-ID: <1244781466-sup-4096@javelin> (raw)
In-Reply-To: <1244735117-sup-6933@ntdws12.chass.utoronto.ca>
Excerpts from Ben Walton's message of Thu Jun 11 11:46:19 -0400 2009:
> Can you strace/truss/whatever the ruby process running sup to see what
> it's doing?
Seconded. You can attach strace to Sup while it's running, and it
will give you a good fingerprint for what the process is doing when
it locks up.
Cheers,
Edward
prev parent reply other threads:[~2009-06-12 4:38 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
2009-06-11 19:09 ` Marcus Williams
2009-06-12 4:38 ` Edward Z. Yang [this message]
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=1244781466-sup-4096@javelin \
--to=ezyang@mit.edu \
/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