Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site amdcad.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxj!ihnp4!amdcad!phil
From: phil@amdcad.UUCP (Phil Ngai)
Newsgroups: net.news.b
Subject: Re: expire takes 73 minutes of cpu?!?!?
Message-ID: <280@amdcad.UUCP>
Date: Tue, 20-Nov-84 15:26:28 EST
Article-I.D.: amdcad.280
Posted: Tue Nov 20 15:26:28 1984
Date-Received: Thu, 22-Nov-84 06:13:23 EST
References: <1828@nsc.UUCP> <1859@nsc.UUCP> <1884@nsc.UUCP>
Organization: AMDCAD, Sunnyvale, CA
Lines: 20

I bet Jay thought the date put in the history file would be
derived from the Expires: line or the date of receipt if there
was no Expires: line. If you want even more flexibility, you could
also store the date the article was received.

> In article <3114@utah-cs.UUCP> lepreau@utah-cs.UUCP (Jay Lepreau) writes:
> >Chuq claims that the use of "expire -e N" negates the value of putting
> >the expiration date in the history file.  Huh??  I'm no expert on the
> >news software, but that makes no sense to me.
> 
> here is the situation. Assume we put the expiration date in the history
> file. When a message comes in, we add the DFLTEXP value (say 14 days) to
> the time received to get the expiration time (november 1 becomes november
> 15 for expiration).
-- 
 When you've seen one tree, you've seen them all. -Bonzo Reagan

 Phil Ngai (408) 749-5790
 UUCP: {ucbvax,decwrl,ihnp4,allegra,intelca}!amd!phil
 ARPA: amdcad!phil@decwrl.ARPA