From: Mark Alexander <marka@pobox.com>
To: Jonathan Lassoff <jof@thejof.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] sup Xapian crash
Date: Wed, 02 Jan 2013 16:33:39 -0500 [thread overview]
Message-ID: <1357162160-sup-4225@bloovis.org> (raw)
In-Reply-To: <CAHsqw9uZk4bB0a8mz3ERNVZ7T+jO2zNNwc=+qDQ6dNO+1aYAFw@mail.gmail.com>
Excerpts from Jonathan Lassoff's message of Wed Jan 02 15:26:15 -0500 2013:
> I'm having a sad day with sup. I'm crashing with a Xapian error I'll
> have to dig into.
I've never attempted to debug these kinds of crashes (which I run into
once or twice a year). Instead, I use sup-dump to save the state of
the index, rename .sup/xapian to .sup/xapian.bad, then use sup-sync
--restore to rebuild the index.
Even though sup is not maintained, I'm so addicted to it that I'm willing
to put up with this inconvenience once in a while.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2013-01-02 21:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 20:26 Jonathan Lassoff
2013-01-02 21:33 ` Mark Alexander [this message]
2013-01-02 23:20 ` Jonathan Lassoff
2013-01-03 23:04 ` Mark Alexander
2013-01-04 9:49 ` Jim Cheetham
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=1357162160-sup-4225@bloovis.org \
--to=marka@pobox.com \
--cc=jof@thejof.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