On Sun, 2009-04-26 at 21:40 +0900, Randy Bush wrote: > damn! why did i not think of that? :)
Weeeellll... no, that's just to tempting ;-)
> 4g machines, swapinfo, vmstat, etc show no hints. but it's always in
> exim_tidydb, $dieties know why.
I smell a corrupted DBM file. Can you run exim_tidydb by hand (it won't
hurt) at an appropriate moment and wait to see which db file it opens
when the memory usage goes bananas?
Alternatively, delete or move them aside one by one (again it's unlikely
to hurt much) and see which one "unsticks" the problem. Then, if you
move them, you can have a look-see at the file to see why it's broken.
