W dniu 30.03.2011 16:21, Per Jessen pisze: > Well, isn't the behaviour you're seeing working-as-expected then? If it > was an indefinite loop, setting up a time-out would be a possible > work-around. If the bayes code is doing what it is supposed to do, but > just taking long to do it, no work-around is needed. > Instead, you could try limiting the size of what is being processed by > spamd.
Border case (i don't have much time for SA, i need to know quickly): --timeout-child=1 I start spamc, and i'm expecting after one second i'll get info: -spam -ham -time_limit but know i'm getting info "time limit" after (e.g) 5 seconds.
