root 1096 0.8 0.2 1336 348 ?SJul10 15:40 supervise
qmail-imapd
You have a problem with your supervise supvervising imapd. It could be if
you have alread started the imapd outside supervise and hence supervise is
not able to start it (bind address already in use). If the run
Once you get the CPU back to normal, could you test to see
if the latest vpopmail devel release causes the same problem?
I had changed the signal code in vpopmail to hopefully work
with supervised systems. I don't have supervise running on
any of my test machines, so I can't test it.
Ken Jones
there are 2 qmail-send proceses, one supervised and one alone. I did
configure the qmail like LWQ, so there are a qmail script in init.d and
S***
links in 12345 levels, i also have a qmail-send directory under
/service.Is
this wrong ??
I've had the same problem, it has to do with vpopmail
make sure you are running either the stable version of vpopmail or the latest dev
version as I found that vdelivermail would consume
a 450 Mhz Xeon at 1 concurrent local delivery with vpopmail 4.10.23. There have been
some performance improvments to vdelivermail
since then. Im running 4.10.28
