From: Steve Goldman <sgoldman@tower-research.com>
To: Sup Talk List <sup-talk@rubyforge.org>
Subject: [sup-talk] Switching to Exchange
Date: Thu, 18 Feb 2010 17:56:53 -0500 [thread overview]
Message-ID: <1266533680-sup-7580@sgoldmanlinux.tower-research.com> (raw)
Hey guys,
Thanks for the wild ride, but I need to switch to something more
reliable. Not sure if there are incompatibilities with my version of
ruby or whatnot, but I'm getting ridiculous CPU usage and random seg
faults. It's too much stress for me. And after a crash when I
restart, I have a random collection of seventy or so messages in my
inbox, even though it was zero when I crashed.
This combined with not being able to convert to xapian without a seg
fault...
Maybe I'll be back some day.
Good luck.
--
Steve Goldman
sgoldman@tower-research.com
T: 212.219.6014
F: 212.219.6007
Tower Research Capital, LLC
377 Broadway, 11th Fl.
New York, NY 10013
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2010-02-18 22:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 22:56 Steve Goldman [this message]
2010-02-19 20:57 ` Steve Goldman
2010-02-19 21:28 ` hollunder
2010-02-21 17:40 ` Nicolas Pouillard
2010-02-20 17:38 ` Ben Gamari
2010-02-20 21:10 ` Mark Alexander
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=1266533680-sup-7580@sgoldmanlinux.tower-research.com \
--to=sgoldman@tower-research.com \
--cc=sup-talk@rubyforge.org \
/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