Per Jessen wrote: > Martin Gregorie wrote: >>> Yeah - maybe there is some indication in the log? I think there is >>> a switch that determines how many emails a child will process before >>> needing restart. (just looked it up: --max-conn-per-child) >>> I just checked my logs, during the last 9 hours I have 6016 of >>> these: >>> >>> spamd[11362]: spamd: handled cleanup of child pid 14010 due to >>> SIGCHLD >>> >>> Is that the one you mean? >>> >> That's the only log message I've seen. Sometimes you can associate it >> with a scan that exceeded --timeout-child seconds and sometimes, much >> more rarely, it happens after a scan taking two or three seconds. > > I don't know if that is happening on my systems too, I haven't > checked.
Okay, I ran a check on my logs since midnight - yes, I also see a lot of child processes running for less than 10secs, in fact slightly more than 50%. Interesting issue. /Per Jessen, Zürich
