From: johnbent@lanl.gov (John Bent)
Subject: [sup-talk] two sup crashes
Date: Thu, 07 Aug 2008 07:33:12 -0600 [thread overview]
Message-ID: <1218115911-sup-8006@tangerine.lanl.gov> (raw)
In-Reply-To: <1218046971-sup-1407@entry>
Excerpts from William Morgan's message of Wed Aug 06 12:23:59 -0600 2008:
> Reformatted excerpts from John Bent's message of 2008-08-06:
> > I was sending an email and sup crashed. I restarted, resent the
> > email, and then it crashed again right after I archived some emails,
> > saved the index and tried to refresh my screen. Both errors are below
> > and seem to be related.
>
> Do the same actions work if you restart Sup?
>
Yeah it does.
> These are both Ferret index corruption errors, which means I can either
> debug Ferret, or rewrite Sup to not use it. (I've chosen the latter.)
>
Oh, that's a relief actually. I also sometimes get what I recognize as
Ferret errors and ignore them since I know you're moving away from it.
I just somehow didn't recognize these.
next prev parent reply other threads:[~2008-08-07 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 14:12 John Bent
2008-08-06 18:23 ` William Morgan
2008-08-07 13:33 ` John Bent [this message]
2008-08-07 15:18 ` William Morgan
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=1218115911-sup-8006@tangerine.lanl.gov \
--to=johnbent@lanl.gov \
/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