From: Bud Rogers <budr@sirinet.net>
Subject: Re: gnus with leafnode
Date: 27 Nov 1999 11:33:05 -0600 [thread overview]
Message-ID: <87yabjrga6.fsf@twocups.sirinet.net> (raw)
In-Reply-To: Pieter Wenk's message of "Sat, 27 Nov 1999 16:45:12 +0100"
Pieter Wenk <pwenk@urbanet.ch> writes:
> I made a fes tests with Netscape....this is now working without
> problems. With "localhost". Ther servers (I have two), are in my
> /etc/news/leafnode/config.
Are you actually able to read newsgroups from your leafnode installation
using Netscape or mutt? If so your leafnode setup is probably fine.
>
> Now is it possible, that gnus will need several minutes lets
> say up to a 1/2 hour in order to read ther active file...in which
> is empty ? /var/spool/news/active.read has nothing inside.
>
> Is this normal ?
Hmm. My /var/spool/news/active.read is also empty, so that is probably OK.
I have seen gnus appear to hang up for indefinite periods if I try to read
a newsgroup that is not yet present. That is, if I subscribe to a new
group leafnode puts a dummy message on the server saying that new messages
will be downloaded the next time fetchnews runs. If I catchup that group
and then try to read it again before running fetchnews, or if there are no
new articles in the group after I run fetchnews, gnus hangs up trying to
get the non-existent new articles. Once fetchnews brings down some new
articles for the group, gnus works fine. Could this be what is happening
in your case?
Lars, I had not thought of that as a bug. And I don't know if it would be
considered a bug in gnus or in leafnode. Reading from a real news server
gnus would likely never encounter a newsgroup that was totally empty. But
it is kind of uncool -- perhaps there should be a graceful timeout or
something? If this is worth looking into I will try to help.
--
Bud Rogers <budr@sirinet.net>
next prev parent reply other threads:[~1999-11-27 17:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-26 21:48 Pieter Wenk
1999-11-26 22:48 ` Kai Großjohann
1999-11-26 23:40 ` Pieter Wenk
1999-11-27 11:58 ` Kai Großjohann
1999-11-26 23:34 ` Bud Rogers
1999-11-27 6:57 ` David Maslen
1999-11-27 9:31 ` Pieter Wenk
1999-11-27 12:00 ` Kai Großjohann
1999-11-29 16:56 ` Pieter Wenk
1999-11-27 14:33 ` Bud Rogers
1999-11-27 15:45 ` Pieter Wenk
1999-11-27 17:33 ` Bud Rogers [this message]
1999-11-27 21:53 ` Pieter Wenk
1999-11-27 22:07 ` Bud Rogers
1999-11-28 0:30 ` John Markus Bjorndalen
1999-11-27 23:50 ` Kevin Ryde
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=87yabjrga6.fsf@twocups.sirinet.net \
--to=budr@sirinet.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;
as well as URLs for NNTP newsgroup(s).