I'm still fighting processor usage on one of our internet servers,
5.0.4 with Fast Start. All email clients are POP3 virtual domain
cpuhog shows that popper is what's sucking cycles, and they hang
around forever until they have the whole machine. sar shows idle
of 0% after the machine has been up for 2-3 hours, which is obviously
wrong, as it runs fine and is very quick. It does slow down some,
but nothing like sar says it should be - 97% sys usage. (!)
This is having secondary effects, in that sendmail requires me to keep
upping the queue trigger levels, and sometimes wedges and as to be
restarted. I mentioned more detail on this in an earlier message.
In any case, popper's man page mentions a -d option which pertains to
time-to-livem but it neglects ranges or what the default might be. It
says it gets it from a bvariable in a config file, but I can't find
Most of these users are PPP-dialup, their ping rates are in the low 200
ms range from server-to-client, so WHAT should popper -d be set to so
the damned things will die before they take over the system?
Is there some special tuning I should do to 5.0.4 since I'm running
Fast Start on it? Regular (5.0.2 based) Fast Start 1.0 ran like a
bear- never had these weird little problems with it.
Please do point me somewhere; right now we're dealing with this by
watching it and fixing it by hand, 24/7