Search the FAQ Archives

3 - A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z
faqs.org - Internet FAQ Archives

INN FAQ Part 7/9: Problems with INN already running
Section - (7.54) Expire is slooooooow

( Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Business Photos and Profiles ]


Top Document: INN FAQ Part 7/9: Problems with INN already running
Previous Document: (7.53) Makehistory is slow on inn 1.x , x<5.1
Next Document: (7.55) Why are multiple innwatch's running?
See reader questions & answers on this topic! - Help others by sharing your knowledge
Q: Expire takes 20 hours on my system to complete.

First of all you should call news.daily with the delayrm option (see
also #2.12, #4.18, #4.19, #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.

User Contributions:

Comment about this article, ask questions, or add new information about this topic:

CAPTCHA




Top Document: INN FAQ Part 7/9: Problems with INN already running
Previous Document: (7.53) Makehistory is slow on inn 1.x , x<5.1
Next Document: (7.55) Why are multiple innwatch's running?

Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page

[ Usenet FAQs | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
hwr@pilhuhn.de (Heiko W.Rupp)





Last Update November 21 2011 @ 01:00 PM