How long is this supposed to take? I'm finding with highwater set to 120Mb, it takes upwards of 8-10 hours to prune the database. (linux box, p166 cpu, 128Mb ram) Things wouldn't be so bad if nntpcache allowed users to still read messages while it was doing that, but it doesn't. End result is grumpy customers. FWIW, INN allows readers and feeders to connect right up to the point of switching history databases, so even if expiry takes 8 hours, the server is only unavailable for reading/posting for a couple of minutes. This is a pretty undesirable aspect to nntpcache's behaviour on a multiuser commercial site. AB
