From: Steve Goldman <sgoldman@tower-research.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Problems running sup-convert-ferret-index
Date: Sun, 17 Jan 2010 19:28:12 -0500 [thread overview]
Message-ID: <1263774467-sup-9664@sgoldmanlinux.tower-research.com> (raw)
In-Reply-To: <1263772988-sup-2344@masanjin.net>
Excerpts from William Morgan's message of Sun Jan 17 19:04:46 -0500 2010:
> Reformatted excerpts from Steve Goldman's message of 2010-01-17:
> > ... until it exited thirty minutes later with seg fault.
> >
> > Anyone else see this? Any way to debug it?
>
> Is it possible it's running out of memory?
Possible. I have 4GB and about 60k messages in my index. So it's not
too likely. I'll run it again and watch the usage.
--
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 prev parent reply other threads:[~2010-01-18 0:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 19:50 Steve Goldman
2010-01-17 20:38 ` William Morgan
2010-01-17 21:22 ` Steve Goldman
2010-01-17 21:34 ` William Morgan
2010-01-17 23:38 ` Steve Goldman
2010-01-18 0:04 ` William Morgan
2010-01-18 0:28 ` Steve Goldman [this message]
2010-01-18 1:44 ` Steve Goldman
2010-01-18 2:10 ` Rich Lane
2010-01-18 6:03 ` Anirudh Sanjeev
2010-01-18 17:04 ` William Morgan
2010-01-18 17:27 ` Anirudh Sanjeev
2010-01-18 19:43 ` Steve Goldman
2010-01-18 22:05 ` William Morgan
2010-01-19 13:31 ` Steve Goldman
2010-01-19 13:37 ` William Morgan
2010-01-25 16:34 ` Steve Goldman
2010-01-25 21:30 ` William Morgan
2010-01-25 21:56 ` Steve Goldman
2010-01-26 13:00 ` William Morgan
2010-01-27 3:24 ` Steve Goldman
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=1263774467-sup-9664@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