From: Steinar Bang <sb@metis.no>
Subject: Re: Gnus 5.5 not displaying new articles in group
Date: 22 Mar 1998 18:55:04 +0100 [thread overview]
Message-ID: <whu38qsj9j.fsf@norne.oslo.metis.no> (raw)
In-Reply-To: Stefanie Teufel's message of "Sat, 21 Mar 1998 23:09:20 +0100"
>>>>> Stefanie Teufel <s.teufel@ndh.net>:
> On Sat, Mar 21, 1998 at 07:59:57PM +0100, Steinar Bang wrote:
>> >>>>> Stefanie Teufel <s.teufel@ndh.net>:
>>
>> > Nope. Perhaps I don't understanding you correctly, but my newsspool
>> > resides on a normal Linux native partition and I am running leafnode 1.4.
>> > as my local newsserver, because it's only a single user system. I read
>> > about problems relating to leafnode, though I thought they just occured
>> > with earlier versions?
>>
>> If you read a newsspool maintained with leafnode, using nnspool, how
>> does leafnode know what to fetch, and what to continue to fetch?
> Leafnode itself is the NNTP server. It talks to your news client, and
> stores readership data. Fetch (which comes with leafnode) is the NNTP
> news-gatherer. It looks at the readership data Leafnode stores, and
> selects what groups to pull news from.
[snip!]
I know this. What I meant was:
If you read the leafnode news spool using nnspool, rather than the
nntp back end, how will "fetch" know what to fetch?
next prev parent reply other threads:[~1998-03-22 17:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-09 17:45 Kris Boulez
1998-03-13 21:24 ` Lars Magne Ingebrigtsen
1998-03-13 23:43 ` Stefanie Teufel
1998-03-14 7:29 ` Eze Ogwuma
1998-03-16 8:14 ` Kris Boulez
1998-03-19 12:10 ` Lars Magne Ingebrigtsen
1998-03-19 15:16 ` Stefanie Teufel
1998-03-20 17:48 ` Lars Magne Ingebrigtsen
1998-03-20 18:10 ` Stefanie Teufel
1998-03-21 18:59 ` Steinar Bang
1998-03-21 22:09 ` Stefanie Teufel
1998-03-22 17:55 ` Steinar Bang [this message]
1998-03-22 18:37 ` Kai Grossjohann
1998-03-22 18:53 ` Stefanie Teufel
1998-03-23 13:14 ` Lars Magne Ingebrigtsen
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=whu38qsj9j.fsf@norne.oslo.metis.no \
--to=sb@metis.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).