Gnus development mailing list
 help / color / mirror / Atom feed
From: gnus-bug@ifi.uio.no (The Gnus Bugfixing Girls + Boys)
Subject: Re: Parent of cache directory read-only
Date: 13 Dec 1995 18:30:33 +0100	[thread overview]
Message-ID: <w8sivjkyipy.fsf@gymir.ifi.uio.no> (raw)
In-Reply-To: Pekka Marjola's message of 13 Dec 1995 11:22:30 +0200

Pekka Marjola <marjola@trshp.ntc.nokia.com> writes:

> >> Signalling: (file-error "Opening directory" "permission denied" "/user")
> >> directory-files("..")
> >> gnus-cache-generate-active("..")
> 
> Lars> Hm.  Then you should set `gnus-use-cache' to nil, since gnus-cache
> Lars> really does have to write to the cache directory to work now.
> 
> Certainly I won't, since caching is so useful. Of course, the cache
> directory (set to (expand-file-name "~/News/gnus-cache")) is readable
> and writable, but /user is not readable. 0.18 had no such
> problems...

Sorry; I didn't notice that it was traversing up directories (".."),
which is a bug.  This problem should be gone in September 0.22.

-- 
Your bug processing zombie for the evening has been Lars Magne
Ingebrigtsen.  If you want an explanation on what you have just read,
please refer to <URL:http://www.ifi.uio.no/~larsi/zombie.html>.


           reply	other threads:[~1995-12-13 17:30 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <v5xwx81e2sp.fsf_-_@ace.trs.ntc.nokia.com>]

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=w8sivjkyipy.fsf@gymir.ifi.uio.no \
    --to=gnus-bug@ifi.uio.no \
    /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;
as well as URLs for NNTP newsgroup(s).