INN FAQ Part 7
Be sure to read the "RKT couplings" below for additional information and updates to this entry.
|Subject: (7.54) Expire is slooooooow|
Q: Expire takes 20 hours on my system to complete.
First of all you should call news.daily with the delayrm option (see
also INN FAQ #2.12, INN FAQ #4.18, INN FAQ #4.19, INN FAQ #5.13). If this is still too slow, then it
could be that the list passed to "fastrm" is too large to be sorted by
the sort(1) command, typically because /tmp is too small. Try setting
TMPDIR in innshellvars.
[Source: INN FAQ Part 7 Archive-name: usenet/software/inn-faq/part7]
[Last Changed: $Date: 1997/09/16 01:25:57 $ $Revision: 2.25 $]
[Copyright: 1997 Heiko Rupp, portions by Tom Limoncelli, Rich Salz, et al.]
(Corrections, notes, and links by Mib Software)
It isn't clear why some of those FAQ entries are referenced, but here they are:
2.12 INN FAQ Systems where only root can have "cron" jobs.
4.18 INN FAQ Other cron jobs.
4.19 INN FAQ Cookbook example of setting up NOV ("overchan").
5.13 INN FAQ news.daily reports: "Expire had problems removing articles"
Up to: INN FAQ Table Of Contents for Part 7/9
Up to: Usenet RKT For Providers...Troubleshooting INN
Up to: INN Troubleshooting by Topic: Performance
RKT Rapid-Links:[ Search ] [ RKT Tips ] Path: Usenet RKT / For / INN FAQ / Part 7 / 0062.htm
You are reading from the Usenet RKT
Copyright 1997-1999, Forrest J. Cavalier III, Mib Software
INN customization and consulting