Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site oracle.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!oliveb!hplabs!oracle!news
From: news@oracle.UUCP (USENET Account )
Newsgroups: net.news.adm
Subject: Expiring news articles
Message-ID: <123@oracle.UUCP>
Date: Mon, 21-Oct-85 12:30:02 EDT
Article-I.D.: oracle.123
Posted: Mon Oct 21 12:30:02 1985
Date-Received: Wed, 23-Oct-85 04:12:39 EDT
Organization: ORACLE Corporation, 2710 Sand Hill Rd., Menlo Park, CA 94025
Lines: 32

I need a little more explanation on expiring news articles. We've been
receiving the news now since first of October. I ran expire for the
first time early this morning, and from all expectations, expected 
approx. 50% reduction in my space. It didn't happen. This is, I believe
due to the fact that most of our news is still within the 2 week time
frame of the default.

My questions are thus:

	1) Is 2 weeks a good expiration duration?
	2) If I use the archive option, will readnews be smart
	   enough to look in /usr/spool/oldnews?
	3) Is there an 'archival' scheme, meaning, I'm interested
	   in saving old INTERESTING news in such a fashion that
	   it can be brought back on-line for someone doing research,
	   etc. Is this more hassle than its worth?
	4) Is there a 'locking mechanism' so that 'expire' doesn't
	   collide with 'rnews'? If not, what scheme(s) have you
	   found successful? Is a locking scheme required?
	5) The installation documentation send something about giving
	   certain articles 'long expiration dates'. How is this
	   done?

Thanks in advance for you responses.

-- 
--------------------------------------------------------------------------------
Dave Abbajay
Senior Technical Staff
ORACLE Corporation
(415)854-7350                                    hplabs!oracle!abbajay
--------------------------------------------------------------------------------