[102409] in RedHat Linux List

home help back first fref pref prev next nref lref last post

Re: newsserver PLEASE HELP!

daemon@ATHENA.MIT.EDU (Bob Taylor)
Wed Dec 2 21:18:45 1998

From: Bob Taylor <brtaylor@inreach.com>
To: redhat-list@redhat.com
In-reply-to: Your message of "Wed, 02 Dec 1998 20:40:48 +0100."
             <98120220435700.01468@localhost.localdomain> 
Date: Wed, 02 Dec 1998 18:04:21 -0800
Resent-From: redhat-list@redhat.com
Reply-To: redhat-list@redhat.com

In message <98120220435700.01468@localhost.localdomain>, Jacek Andreas Matulla 
writes:
>  Hi all, 
> 
> since no one responded till now I have to repost.
> 
> I have some problems running leafnode...
> 
> First I'd like to know what's the latest version of it? I'm currently using
> leafnode 1.4-5 on a RH 4.2 system. PII 300 with 64MB + 128MB swap.

Don't know. I'm running 1.5-1 under Red Hat 5.1.

[snip]

> fetch is very slow after having retrieved the articles. I only see much disk
> activity for about 5 minutes or more. Then when trying to read a group with
> netscape I think that lefnode is invoked and the disk activity begins again. 
>It
> then takes up to 10 minutes for the articles of ONLY one group to be retrieve
>d. 
> In this case some 200-400 messages. This repeats for about
> every group. Netscape is showing for one group 40K of messages. It seems that
> the more messages have already been read it takes longer for retrieving
> new messages. I have no idea why it takes so long for fetch/leafnode to
> retrieve/sort the messages.

I have never experienced this. Perhaps it's the USENET server?

> In my /var/log/messages I have a line like this:
> Nov 27 19:43:31 localhost fetch[535]: writev() for .overview failed: Invalid 
>argument
> 
> Nov 27 20:10:33 localhost leafnode[631]: writev() for .overview failed: Inval
>id
> argument
> 
> What do this messages want say me?

I don't recall seeing these messages either.

> How can I make leafnode faster?

Upgrade. If there isn't any change try another USENET server and see if
there is any change. BTW, one other possibility is you just have a slow/
overloaded link.

> Then lefnode does not remove the messages as it should. They should expire in
> 5
> days which should leave 10000 messages max. But I have always about 40000
> messages and texpire does not remove them...

Did you add texpire to cron? I have texpire executable in /etc/cron.daily.
Also check your /usr/lib/leafnode/config file. Specifically the expire and
groupexpire variables.

> Is there any other newsserver with similar easy configuration as leafnode?

Most probably. I've never tried any since I have been quite happy with
leafnode.

Bob

-- 
+---------------------------------------------------------------+
| Bob Taylor             Email: brtaylor@inreach.com            |
|---------------------------------------------------------------|
| Like the ad says, at 300 dpi you can tell she's wearing a     |
| swimsuit. At 600 dpi you can tell it's wet. At 1200 dpi you   |
| can tell it's painted on. I suppose at 2400 dpi you can tell  |
| if the paint is giving her a rash. (So says Joshua R. Poulson)|
+---------------------------------------------------------------+



-- 
  PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
		http://www.redhat.com http://archive.redhat.com
         To unsubscribe: mail redhat-list-request@redhat.com with 
                       "unsubscribe" as the Subject.


home help back first fref pref prev next nref lref last post