There is something else amiss here, from my reading of the logs. If there is gobs of memory available, then do as Sam suggests and allocate a LOT - say 300mb to the softlimit and retest. I'd wager there will still be troubles.
On 6/9/2011 11:54 AM, spamdyke-users-requ...@spamdyke.org wrote: > So instead of hitting the spamdyke timeout, it hit a timeout on the i/o > operation. Still doesn't point to the root cause. :( > Why softlimit doesn't issue some sort of error message is beyond me. I'm > still inclined to ditch it. _______________________________________________ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
