At 5:22 PM -0500 10/29/06, Peter Kofod wrote:
I wouldn't even have started looking in to it if it wasn't that the system was so unresponsive.
That's not unusual. Most systems get completely ignored unless there is some sort of catastrophic problem.
It literally took 20 minutes to get a login prompt via ssh today. This was with no mail being processed. The only way it gets quick again is when I kill the pid for mailmanctls and all her "kids". Something is bogging it down and it's not the MTA (postfix) or apache, since it is still slow after I kill those as well.
From what you've said so far, it seems likely that Mailman is somehow involved in whatever problems you're having, but it's hard to say whether it's an innocent bystander that is suffering from collateral damage caused by something else, or if Mailman is actually the root cause (or one of the root causes).
Any thoughts on what it means when the process is in a wa (wait?) state as opposed to id (idle?).
You'd need to have experience in kernel and thread programming on your particular platform in order to have a better idea of what this means. I'm not a programmer, and I don't have much Linux-specific knowledge, so I'm afraid that I can't help you there.
-- Brad Knowles, <brad@shub-internet.org>
Trend Micro has announced that they will cancel the stop.mail-abuse.org mail forwarding service as of 15 November 2006. If you have an old e-mail account for me at this domain, please make sure you correct that with the current address.