Pernicious problem with vfork / qmail / qmail-scanner

Hello list, I am having a hell of a time with qmail/qmail-scanner, and I am hoping someone on the list can help me. Normally this setup has worked completely fine on any FreeBSD machine I've set it up on. This is on 5.1-p10 (which I'm still running as I've yet to upgrade to 5.2.1R, and I am wo

Re: Pernicious problem with vfork / qmail / qmail-scanner

This error means means you`ve run out of memory (RAM + swap). Add RAM or swap, or lower your concurrencies or stop unneeded processes. Have you checked your memory? Qmail-scanner is *very* resource intensive as it is a huge perl program, which then calls KAV, and I have a feeling this is where the

Pernicious problem with vfork / qmail / qmail-scanner (RESOLVED)

Justin Baugh wrote: I did some testing. I wrote a small program in C to fork off a specified number of processes and leave them there. I find that I can run exactly 39 processes as qmaild before tcpserver begins to barf, saying it cannot fork. So, after much testing & debugging: * The problem

Re: Pernicious problem with vfork / qmail / qmail-scanner (RESOLVED)

Happen to catch this, this morning... Good dig on this.. Tcpserver *defaults* to a maximum of 40 simultaneous connections, so this could very well be where your problem is.. Sorry, should have thought of this earlier. You can raise this limit with the -c n (n=number) option.. Please see