From: Jonathan Lassoff <jof@thejof.com>
To: Mark Alexander <marka@pobox.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] sup Xapian crash
Date: Wed, 2 Jan 2013 15:20:28 -0800 [thread overview]
Message-ID: <CAHsqw9vha-C=g-nrcvA_dNMGjsfmz8+chOWXvq7e0N0Ns5KM0A@mail.gmail.com> (raw)
In-Reply-To: <1357162160-sup-4225@bloovis.org>
On Wed, Jan 2, 2013 at 1:33 PM, Mark Alexander <marka@pobox.com> wrote:
> 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.
I started digging, but got bored with reading about the Xapian APIs,
so I mostly did what you just did as well :P
However, I needed to perform a sup-sync first to create the index and
add the messages in, so when I restored from the dump, pretty much
everything was marked as unread.
Working in the console to declare inbox bankruptcy and inbox zero, and
just clearing it all out. Thank goodness I'm starring threads that I
need to follow up on! :p
> 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.
Yeah, I've been using sup for so long that I can't just let it go now.
I've got all these excellent hooks and I know the system well.
Have you looked at Heliotrope / Turnisole yet?
That totally seems like wmorgan's future mail architecture, and I've
been curious to migrate to it, but haven't been able to sink the time
into it just yet.
Cheers,
jof
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2013-01-02 23:20 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
2013-01-02 23:20 ` Jonathan Lassoff [this message]
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='CAHsqw9vha-C=g-nrcvA_dNMGjsfmz8+chOWXvq7e0N0Ns5KM0A@mail.gmail.com' \
--to=jof@thejof.com \
--cc=marka@pobox.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