> > Thats really odd. Especially it being in the parent process. Have > > you made any customizations? The forkserver doesn't really do > > anything interesting in the parent except fork. > > Nope. No customizations to qpsmtpd-forkserver. (To be clear, this is the > process that does the accept(). So, it actually does some work, I > believe.)
Ok, fork and accept. Are you using MAXCONNIP? If so, you might want to try turning it off, as that is the largest chunk of easily disable-able code that runs in forkserver. It still doesn't really do anything beyond accept, some sockaddr_in, and hashtable modifications. (And the child handling stuff.) The child handling stuff (REAPER) is likely the culprit. Signal handling is always good to blame. I'm pretty sure 5.8.6 has safe signals on by default. > Our server is under tremendous load because of the recent virus > attacks. We haven't been seeing anything terribly bad. (Although there's definitely been leakage into my inbox.) -R
