Gnus development mailing list
 help / color / mirror / Atom feed
From: Pieter Wenk <pwenk@urbanet.ch>
Subject: Re: gnus with leafnode
Date: Sat, 27 Nov 1999 22:53:06 +0100	[thread overview]
Message-ID: <19991127225306.B2658@sre-4-139.urbanet.ch> (raw)
In-Reply-To: <87yabjrga6.fsf@twocups.sirinet.net>

Hallo Bud,

>Are you actually able to read newsgroups from your leafnode installation
>using Netscape or mutt?  If so your leafnode setup is probably fine.

Yes. Under Netscape I have subscribed a certain number of
NG..After having fired fetchnews...I can now read, mail etc.,
Under Netscape it works...and with the nifty mutt I have
also no problems.


>> 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.

Bud I tried to put read-active file to 'some. But this was
not a good idea. I was gratified with a crash of gnus and xemcas.

But I do not think this is a bug...I guess it's just not possible
setting 'some with the setup I have.


>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.

I did run fetchnews again during this after-noon. I have something
like 30 subscribed NG...some have quite trafic. But, the correspon-
ding messages "were fetched".



  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?

Hmm. I just fetched this after-noon. I have in fact no buggy NG's
subscribed, some of them I know since years. I just can understand
that it's taking "ages" in getting these subscribed NG under
gnus in form of the usual Group-Summary.

When I am talking "hanging", it seems that gnus is reading
the active file from nntp server, which is localhost. 
During this period, it's not possible to give "any" commands.
It's just sucking...

Under Netscape these groups were read within minutes...

I run a 586 Machine with 64 RAM.

Do you have an idea, why this is taking so long ?

And I still have not as yet the "Group Summary".

Many thanks

Regards
--- 
        
                           / /  (_)____ __ ____  __
      Pieter Wenk         / /__/ / _ \/ // /\ \/ /  Vevey/Switzerland
                         /____/_/_//_/\_,_/ /_/\_\




  reply	other threads:[~1999-11-27 21:53 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
1999-11-27 21:53           ` Pieter Wenk [this message]
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=19991127225306.B2658@sre-4-139.urbanet.ch \
    --to=pwenk@urbanet.ch \
    /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).