From owner-freebsd-isp Sat Oct 5 00:59:37 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA02008 for isp-outgoing; Sat, 5 Oct 1996 00:59:37 -0700 (PDT) Received: from al.imforei.apana.org.au (pjchilds@al.imforei.apana.org.au [202.12.89.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA02002 for ; Sat, 5 Oct 1996 00:59:28 -0700 (PDT) Received: (from pjchilds@localhost) by al.imforei.apana.org.au (8.8.0/8.7.3) id RAA09217; Sat, 5 Oct 1996 17:29:15 +0930 (CST) Date: Sat, 5 Oct 1996 17:29:15 +0930 (CST) From: Peter Childs Message-Id: <199610050759.RAA09217@al.imforei.apana.org.au> To: dror@dnai.com (Dror Matalon), freebsd-isp@freebsd.org Subject: Re: How to solve the news server problem X-Newsreader: TIN [version 1.2 PL2] Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk : I believe that my news server is spending most of its time receiving, : writing to disk, organizing, and then removing files that NONE OF : MY USERS WILL EVER LOOK AT. Yup :) : We could quite easily figure out which newsgroups our users subscribe : to, accept only articles for these newsgroups and reduce the traffic, : the disk space, the memory etc to ... 5%? 10%? 30%? The problem is : that we want to have newsgroups available when our users want to : subscribe to something new. This works ok in some cases, but not really when your other sites expect you to provide them with a full feed. [cut] : But I couldn't find anyone using this. So folks, is this a good solution? Could work for you. But your still receiving all that news. You want something that limits your newsfeed. Somethings you could look at are "nntpcache" which if you had a nice fast link to your "next-in-line" for news, and you could convince all your "under-feeds" to use would create similar to a distributed "web-cache" type setup. Another product I believe works similar to this (but different) is LeafNode.... from the LeafNode readme. --quote-- Only groups that someone has been reading in the past week are fetched from the upstream NNTP server. When someone stops reading a group, fetch will stop reading that group a week later, and when someone starts reading a group, fetch will grab all the articles it can in that group the next time it runs. --end-quote-- I would still probably opt for using inn with something like "suck" and use the same type of algorithm for determining what you pull from your "up-sites". Co-ordinating this automagically with with sites you feed might be a bit of a problem, but i'm sure you could figure it out :) Peter -- Peter Childs --- http://www.imforei.apana.org.au/~pjchilds Finger pjchilds@al.imforei.apana.org.au for public PGP key Drag me, drop me, treat me like an object!