From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: reading the cache directly, can i just nnspool it?
Date: 19 Apr 1996 21:53:05 +0000 [thread overview]
Message-ID: <w8s20ljx4n2.fsf@trym.ifi.uio.no> (raw)
In-Reply-To: Greg Stark's message of (unknown date)
Greg Stark <gsstark@mit.edu> writes:
> So i tried this:
>
> (nnspool "cache"
> (nnspool-spool-directory "/mit/gsstark/News/cache")
> (nnspool-nov-directory "/mit/gsstark/News/cache")
> (nnspool-lib-dir "/mit/gsstark/News/cache")
> (nnspool-active-file "/mit/gsstark/News/active"))
I think the last should be "/mit/gsstark/News/cache/active".
> I get this:
> Couldn't request list: Opened server cache using directory /mit/gsstark/News/cache
>
> This isn't really the most useful error message,
Not very, no. 0.96 should give better errors here. I have a feeling
that quite a lot of the backend functions give bogus error messages.
Could y'all let me know when that happens so I can fix that?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
prev parent reply other threads:[~1996-04-19 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-04-19 17:21 Greg Stark
1996-04-19 21:53 ` Lars Magne Ingebrigtsen [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=w8s20ljx4n2.fsf@trym.ifi.uio.no \
--to=larsi@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).