On Wed, 2006-09-06 at 17:35 +0100, Justin Mason wrote: > > That looks bad :( The strace snippet, however, is pretty normal-looking. > > First off, are you using an up-to-date 3.1.x release? > Yes, version 3.1.4.
> Secondly, you need to strace both the child *and* the parent spamd process > -- the easiest way to do this is to "strace -f" the parent spamd, then > kill -15 the kids so it starts new (traced) ones. > Okay, I did that. It ran for a few minutes and produced a 10MB file. What is odd is that while strace was running the log file shows for the child states: =============================================================== prefork: child states: BB prefork: child states: BS prefork: child states: BBS prefork: child states: BBBS prefork: child states: BBBBS prefork: child states: BBBBBS prefork: child states: BBBBBBS prefork: child states: BBBBBBBS prefork: server reached --max-children setting, consider raising it prefork: child states: BBBBBBBB prefork: server reached --max-children setting, consider raising it prefork: child states: BBBBBBBB prefork: server reached --max-children setting, consider raising it prefork: child states: BBBBBBBB prefork: server reached --max-children setting, consider raising it prefork: child states: BBBBBBBB =============================================================== This then goes on for quite a bit, but the child state remains at 'BBBBBBBB'. Now that I have stopped strace, the state is: =============================================================== prefork: child states: BIKKKKKK prefork: child states: IIKKKKKK prefork: child states: IIKKKKKK prefork: child states: IIKKKKKK prefork: child states: IBKKKKKK =============================================================== John. -- --------------------------------------------------------------- John Horne, University of Plymouth, UK Tel: +44 (0)1752 233914 E-mail: [EMAIL PROTECTED] Fax: +44 (0)1752 233839
