Theo Van Dinter writes: > On Thu, Aug 17, 2006 at 04:54:20PM +0100, Justin Mason wrote: > > since then, the ArchiveIterator code has been extended to support > > glob-patterns and recursion (I think, not quite sure about the latter) -- > > so now, the user may not have specified the directory at all. > > It doesn't do recursion, but yeah, spam:detect:/path/to/spam/* is > acceptable. As I said, I guess the warn doesn't really matter in the > end, though my personal POV is that I'd want to know there's some random > empty directory that I can remove. > > <shrug>
well, in my case, that stuff is all automated -- I don't intend to bother deleting empty dirs ;) > > by the way, it appears performance on the zone has gone to crap :( 1 hour > > to scan the mass-check corpora, with AI caching on? that's atrocious! > > fwiw, I have a generally idle dual 2.8GHz Xeon server w/ 4GB of RAM that I've > been trying to find something to do with... ;) My original plan was to get > around to doing multi-machine mass-checks, but thoughts about how to do it > haven't fully congealed in my head yet. The only thing is, I think infrastructure would prefer that we used ASF machines... but given the up-and-down nature of the zone, maybe it would be best to offload our load. I wonder. Main thing about the preflight/ruleqa stuff is that it's very heavy on disk space -- I think it's using about 20GB between uploaded corpora and raw XML/gzipped logs used to drive the ruleqa app, and that's only going to go up... --j.
