Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Ferret Errors
Date: Thu, 01 Nov 2007 19:32:19 -0700	[thread overview]
Message-ID: <1193970558-sup-3687@south> (raw)
In-Reply-To: <1193693839-sup-8512@chris-tablet>

Excerpts from Christopher Warrington's message of Mon Oct 29 14:40:37 -0700 2007:
> I'm getting odd ferret errors, usually when I am composing messages in
> nano.
> 
> I suspect that it has something to do with the fact that I am running
> sup under cygwin on Windows...
> 
> Here's the exception:
> --- IOError at Mon Oct 29 16:27:51 -0500 2007
> IO Error occured at <except.c>:117 in xpop_context
> Error occured in fs_store.c:70 - fs_exists
>     checking existance of /home/chrisw/.sup/ferret/_g9c.cfs: <Permission denied>

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)
- 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.
- running out of disk space.

Could it have been any of those?

-- 
William <wmorgan-sup at masanjin.net>


  reply	other threads:[~2007-11-02  2:32 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 [this message]
2007-11-13  4:30   ` Christopher Warrington

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=1193970558-sup-3687@south \
    --to=wmorgan-sup@masanjin.net \
    /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