From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] Sup locking up
Date: Thu, 11 Jun 2009 07:23:49 -0400 [thread overview]
Message-ID: <1244719333-sup-9770@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <1244710855-sup-1368@tomsk>
Excerpts from Marcus Williams's message of Thu Jun 11 05:05:38 -0400 2009:
> Anyone else seeing this (running next branch)?
No...and I'm running from the most recent next with a few local
patches (message bouncing, currently). I run in screen as well.
Is there anything constant about when the lockup occurs? Has anything
else about your system/setup changed that could impact this?
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/20090611/8810e1f0/attachment.bin>
next prev parent reply other threads:[~2009-06-11 11:23 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 [this message]
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
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=1244719333-sup-9770@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