(this was also posted to spamassassin-general, but I thought somebody here might just recognize the problem). I have a very unusual situation (I think): I am running the exact same system (it was cloned) on several single-core and dual-core systems. The only difference is in the hardware, i.e. some systems are dual-core. (ok, there are more differences than that). I am running spamd with maxchild=25 (the actual number in use is controlled externally). The single-core systems vary from two to five, sometimes six. Perfectly normal. On the dual-core systems, I never see more than two active children. Not normal. So I checked the logs - excerpt from a single-core system: spamd[3736]: spamd: handled cleanup of child pid 20940 due to SIGCHLD spamd[3736]: spamd: server successfully spawned child process, pid 20980 spamd[3736]: spamd: server successfully spawned child process, pid 20981 spamd[3736]: spamd: handled cleanup of child pid 20981 due to SIGCHLD spamd[3736]: spamd: handled cleanup of child pid 20980 due to SIGCHLD spamd[3736]: spamd: server successfully spawned child process, pid 21014 spamd[3736]: spamd: server successfully spawned child process, pid 21015 spamd[3736]: spamd: server successfully spawned child process, pid 21017 spamd[3736]: spamd: server successfully spawned child process, pid 21023 spamd[3736]: spamd: handled cleanup of child pid 21023 due to SIGCHLD spamd[3736]: spamd: handled cleanup of child pid 21017 due to SIGCHLD spamd[17254]: (child processing timeout at /usr/sbin/spamd line 1262, <GEN6653> line 27. spamd[3736]: spamd: handled cleanup of child pid 21015 due to SIGCHLD spamd[3736]: spamd: handled cleanup of child pid 21014 due to SIGCHLD excerpt from a dual-core system: spamd[3909]: spamd: server successfully spawned child process, pid 2092 spamd[3909]: spamd: server successfully spawned child process, pid 3439 spamd[3909]: spamd: child 3439 killed successfully spamd[3909]: spamd: child 32574 killed successfully spamd[3909]: spamd: server successfully spawned child process, pid 4249 spamd[3909]: spamd: server successfully spawned child process, pid 4250 spamd[3909]: spamd: server successfully spawned child process, pid 6249 spamd[3909]: spamd: server successfully spawned child process, pid 8242 spamd[6249]: (child processing timeout at /usr/sbin/spamd line 1262, <GEN6864> line 28. spamd[3909]: spamd: server successfully spawned child process, pid 10219 spamd[8242]: (child processing timeout at /usr/sbin/spamd line 1262, <GEN4734> line 28. spamd[3909]: spamd: child 8242 killed successfully spamd[3909]: spamd: child 10219 killed successfully spamd[3909]: spamd: server successfully spawned child process, pid 11091 spamd[3909]: spamd: server successfully spawned child process, pid 11092 spamd[11091]: (child processing timeout at /usr/sbin/spamd line 1262, <GEN1403> line 27. spamd[11091]: (child processing timeout at /usr/sbin/spamd line 1262, <GEN2867> line 28. spamd[3909]: spamd: server successfully spawned child process, pid 13141 spamd[3909]: spamd: child 13141 killed successfully Notice that the single-core system reports "handled cleanup of child pid nnnnn due to SIGCHLD" which is never seen on the dual-core system, and that the dual-core reports "child nnnnn killed successfully", which is never seen on the single-core system. What am I missing here? /Per Jessen, Zürich -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org