fletcher@cs.utexas.edu (Fletcher Mattox) (07/07/89)
If I were to drop the cnews expire into a 2.11.17 system, it looks like the only compatibilty issues would be: 1. locking -- need to have the cnews expire flock (a BSD system) the active file 2. Expires: headers would be ignored because 2.11 wouldn't put that data into the history file. Though it looks like it wouldn't be difficult to get 2.11 inews to insert a cnews expiry field in the history file ... Hmm. Have I overlooked anything? Comments?
larry@nstar.uucp (Larry Snyder) (07/01/90)
nstar is now running cnews - and we have noticed that
expire is not killing articles that have an "Expires in"
line in them unless expire is ran after the date in the
"Expires in" field - is there an option to expire everything
regardless of the contents?
--
Larry Snyder, Northern Star Communications, Notre Dame, IN USA
uucp: iuvax!ndmath!nstar!larry -or- larry@nstar
Public Access Unix Site (219) 289-3745 / lots of files & free PEP feeds!henry@zoo.toronto.edu (Henry Spencer) (07/02/90)
In article <1990Jul01.153715.6850@nstar.uucp> larry@nstar.uucp (Larry Snyder) writes: >...expire is not killing articles that have an "Expires in" >line in them unless expire is ran after the date in the >"Expires in" field - is there an option to expire everything >regardless of the contents? See the expire(8) manual page for details on how to set bounds on expire's acceptance of explicit expiry dates. The out-of-the-box default is a 90-day limit on everything, but it's possible to be more restrictive on a group-by-group basis. There is *sometimes* a real reason to postpone expiry of an article; you probably do not want to just suppress all explicit expiry dates without thinking about it. -- "Either NFS must be scrapped or NFS | Henry Spencer at U of Toronto Zoology must be changed." -John K. Ousterhout | henry@zoo.toronto.edu utzoo!henry
chris@vision.uucp (Chris Davies) (01/30/91)
Well, we've just gone over to CNews. No major problems yet :-)
However, as regards expiring articles, there is a problem. Expire (as
documented somewhere) uses an upper bound for determining the expiry date of
articles. Unfortunately this behaviour does not always seem to be the most
useful. First, part of our "ideal" expiry list:
--> /expired/ x 28 -
--> /bounds/ x 0-1-21 -
-->
--> # Keep alt.* for 7 days except the mega-high-volume groups
--> alt x 7 -
--> alt.desert-shield x 3 -
--> alt.desert-storm x 3 -
-->
--> # People like to read soc.british only every few days
--> soc x 4 -
--> soc.british x 7 -
-->
--> # Keep the disk space under some sort of control
--> all x 21 -
The upper bound rule means that the two newsgroup-specific alt lines are
ignored.
I don't want to change the alt lines as follows, since there is a similar
situation with about 30 comp groups and the problem would remain there too -
--> alt,!alt.desert-shield,!alt.deset-storm x 7 -
--> alt.desert-shield x 3 -
--> alt.desert-storm x 3 -
Changing to behaviour of expire so that it uses the lower bound for determining
the expiry date would not help, because of the entries for soc and soc.british.
(1) Can anyone suggest a way round this? More details on request (I hope I've
given enough info here, tho').
The latest patchdate here is (only) 25-May-1990 (that's all that the "local"
archive server had).
(2) How many patches have there been since then?
Finally, I don't want the default behaviour for CNews to automagically
create groups in response to newgroup/checkgroup messages from all and sundry.
(3) Before I go messing around in -/newsbin/ctl, I'd appreciate it if anyone
who's done this would email me (so I can get the changes just once :-)
Many thanks,
Chris
--
VISIONWARE LTD | UK: chris@vision.uucp JANET: chris%vision.uucp@ukc
57 Cardigan Lane | US: chris@vware.mn.org BANGNET: ...!ukc!vision!chris
LEEDS LS4 2LE, England | VOICE: +44 532 788858 FAX: +44 532 304676
-------------- "VisionWare: The home of DOS/UNIX/X integration" -------------henry@zoo.toronto.edu (Henry Spencer) (02/01/91)
In article <1991Jan30.114829.12010@vision.uucp> chris@vision.UUCP (Chris Davies) writes: >However, as regards expiring articles, there is a problem. Expire (as >documented somewhere) uses an upper bound for determining the expiry date of >articles. Unfortunately this behaviour does not always seem to be the most >useful. First, part of our "ideal" expiry list: > >--> /expired/ x 28 - >--> /bounds/ x 0-1-21 - >--> >--> # Keep alt.* for 7 days except the mega-high-volume groups >--> alt x 7 - >--> alt.desert-shield x 3 - >--> alt.desert-storm x 3 - > >The upper bound rule means that the two newsgroup-specific alt lines are >ignored. I think you have a misunderstanding here. The /bounds/ line is doing nothing of the sort. What *does* render the newsgroup-specific alt lines useless is that you've got a line covering all of alt preceding them. Please reread the expire manpage, notably this part: The first line of the control file which applies to a given article is used to control its expiry. >The latest patchdate here is (only) 25-May-1990 (that's all that the "local" >archive server had). >(2) How many patches have there been since then? Seven (and an eighth probably imminent). You should probably try to get a more up-to-date copy. >Finally, I don't want the default behaviour for CNews to automagically >create groups in response to newgroup/checkgroup messages from all and sundry. Well, we don't create groups in response to checkgroups. However, we do do it for newgroup. Various people have posted mods to this, and something "official" will probably be along when we find time. We rate this as low priority, since creation of a group is a relatively-harmless nuisance. -- If the Space Shuttle was the answer, | Henry Spencer at U of Toronto Zoology what was the question? | henry@zoo.toronto.edu utzoo!henry