> 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. Tuning would be easier if there was some indication about why a scan had terminated - maybe it could be added to the statistics list in the 'results' log line.
> There are also arguments for controlling minimum/maximum number of spare > child processes - if your load varies, and you have a significant > difference between min and max, I could see that leading to more child > processes stopping and starting. > Does the parent or the child determine whether the child stays alive after completing a scan or whether it should terminate? Martin
