Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!samsung!umich!ox.com!emv From: zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) Newsgroups: comp.archives Subject: [news.software.b] Re: Steady state news. Message-ID: <1990Dec15.220819.25783@ox.com> Date: 15 Dec 90 22:08:19 GMT References: <1990Dec12.020442.4407@lokkur.dexter.mi.us> Sender: emv@ox.com (Edward Vielmetti) Reply-To: zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) Followup-To: news.software.b Organization: Branch Technology Lines: 23 Approved: emv@ox.com (Edward Vielmetti) X-Original-Newsgroups: news.software.b Archive-name: news/c/automatic-expire/1990-12-12 Archive: ais.org:/pub/cnews.speedups.Z [141.211.206.16] Original-posting-by: zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) Original-subject: Re: Steady state news. Reposted-by: emv@ox.com (Edward Vielmetti) >>Why not expire constantly? Every time you receive some articles, >>remove some other articles and free an equivalent amount of space. > >We've recently gone to twice-daily expires. Since Cnews expire >runs so quick, it's not been a significant load on the systems and >had done wonders to level out disk usage in /usr/spool/news. We I went to automatic, on demand, expires (run from rnews) a long time ago. Much better than any kind of guessing needed disk space approach. I agree that a smarter continuous expire could be even more efficient (and more difficult to implement). Sources are available via anon ftp from ais.org:~ftp/pub/cnews.speedups.Z -- Jon Zeeff (NIC handle JZ) zeeff@b-tech.ann-arbor.mi.us