Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Fwd: Re: [Ferret-trac] #279: IO Error - Error reading the segment infos
Date: Tue, 14 Aug 2007 22:17:46 -0700	[thread overview]
Message-ID: <1187154980-sup-1906@south> (raw)

Fore those following the index.c:901 error, here's a potential reason
why Ferret might be doing this: too many open filehandles. If you can
reproduce this, try increasing the max open filehandle limit and see if
that helps things.

--- Begin forwarded message from Ferret ---
From: Ferret <trac at davebalmain.com>
Cc: dbalmain <dbalmain at gmail.com>
Date: Wed, 15 Aug 2007 05:52:27 -0000
Subject: Re: [Ferret-trac] #279: IO Error - Error reading the segment infos

#279: IO Error - Error reading the segment infos
--------------------------------------+-------------------------------------
  Reporter:  dennis at dennisschaaf.com  |       Owner:  somebody
      Type:  defect                   |      Status:  reopened
  Priority:  major                    |   Milestone:          
 Component:  component1               |     Version:          
Resolution:                           |    Keywords:          
--------------------------------------+-------------------------------------
Comment (by dennis at dennisschaaf.com):

 This guy mentions that there seems to be a limit with too many open files.
 Could it be that ferret is not closing files properly? I don't know where
 in the source i'd look but i'll try.

 http://www.ruby-forum.com/topic/120609

--- End forwarded message ---

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


             reply	other threads:[~2007-08-15  5:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-15  5:17 William Morgan [this message]
2007-08-18 12:18 ` [sup-talk] " jeff covey
2007-08-27 20:32   ` William Morgan
2007-08-28 21:48     ` jeff covey

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=1187154980-sup-1906@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