Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: chrisw@rice.edu (Christopher Warrington)
Subject: [sup-talk] Possible fix for ferret "Permission denied" errors
Date: Sun,  3 Feb 2008 02:11:11 -0600	[thread overview]
Message-ID: <1202026272-3432-1-git-send-email-chrisw@rice.edu> (raw)


In the forthcoming patch, I have proposed a possible fix for the ferret 
"Permission denied" error some have been getting.

I run sup under Cygwin. Before, when I was composing an e-mail and sup 
did a background poll and found new messages, sup would crash with the 
ferret error "Permission denied".

I think that this has to do with Windows different file sharing 
semantics. I've been running with this patch for a while now and not had 
another "Permission denied" error.

However, I have not been able to test it on a non-Cygwin setup. I also 
don't know if this is the proper way to address this issue. To me, it 
seems mery much like a hack. Is there a clean way to either close all 
open files, get a list of FDs in use, or get the maximum FD allowed?

Comments welcome and encouraged!


                 reply	other threads:[~2008-02-03  8:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1202026272-3432-1-git-send-email-chrisw@rice.edu \
    --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