Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!caip!ll-xn!mit-amt!mit-eddie!genrad!decvax!decwrl!glacier!adobe!shore
From: shore@adobe.UUCP
Newsgroups: net.news.adm
Subject: non-expiring newsgroups
Message-ID: <1504@adobe.UUCP>
Date: Tue, 22-Jul-86 19:20:45 EDT
Article-I.D.: adobe.1504
Posted: Tue Jul 22 19:20:45 1986
Date-Received: Thu, 24-Jul-86 01:45:28 EDT
Reply-To: shore@adobe.UUCP (Andrew Shore)
Organization: Adobe Systems, Palo Alto
Lines: 25


Here at Adobe, we have several local newsgroups (e.g.,
adobe.*) which we never expire.  I'm wondering how advisable
this is, and what if anything I should do to keep news happy.  

Obviously, these groups take up an ever-increasing amount of disk
space in the spool directory.  The articles in them also require
entries in the active and history files.  I currently have about
600 articles total in the adobe.* groups.  These seem to take up
about 46k bytes out of a 596k history file (we expire everything
else in a 15 day cycle).  My nightly runs of expire have to read
(and ignore) all those history lines, etc.

Are there any gotcha's I should be looking out for?
[I'm aware (and fixed) the AFSIZE problem.]
Is there any way to avoid this expire overhead for 
groups which never expire?  Am I crazy for using this scheme?

For those who need to know, we are running 4.2BSD on a VAX 11/750
with news B 2.10.2 9/18/84.

Thanks in advance,
--Andy Shore
  Adobe Systems Incorporated
  {glacier, decwrl, sun}!adobe!shore