From: chrisw@rice.edu (Christopher Warrington)
Subject: [sup-talk] Ferret Errors
Date: Mon, 12 Nov 2007 22:30:13 -0600 [thread overview]
Message-ID: <1194928185-sup-2189@chris-tablet> (raw)
In-Reply-To: <1193970558-sup-3687@south>
(So, this has been sitting in my drafts folder FOREVER...)
Excerpts from William Morgan's message of Thu Nov 01 21:32:19 -0500 2007:
> Yeah, the typical completely incomprehensible Ferret error message.
> Current known things that make Ferret generate scary messages:
> - running more than one process touching the index at the same time (Sup
> locks the index now so this shouldn't happen unless you are being
> particularly devious)
Perhaps... I'm not explicitly running two copies of sup, nor am I
running sup and another sup- tool at the same time. I'm just composing a
message.
> - having too many open filehandles, including too many "usual" mbox
> sources at the moment until I fix the mbox code not to keep
> filehandles open all the time.
I don't think so.
> - running out of disk space.
Nope.
> Could it have been any of those?
If MIGHT be the first. It just happened again. I think that it only
happens when I am composing a message and, during a background poll for
new messages, sup finds one.
This might not even be the problem, but, it seems to me, that the editor
does not need to have sup's open files handles.
--
Christopher Warrington <chrisw at rice.edu>
prev parent reply other threads:[~2007-11-13 4:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 21:40 Christopher Warrington
2007-11-02 2:32 ` William Morgan
2007-11-13 4:30 ` Christopher Warrington [this message]
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=1194928185-sup-2189@chris-tablet \
--to=chrisw@rice.edu \
/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