Hi folks, having installed ISPConfig as described in http://www.howtoforge.com/perfect_setup_debian_etch I am - with an increasing number of users - now slowly running into problems because of the "numproc" restriction on my vServer. The system is obviously an OpenVZ box with the maximum number of processes set to 128. Having talked to the hosting company I now know that there is no chance to adjust this limit... :-/ So I am looking through my process list and wonder where I can effectively reduce the number of running processes. Courier and Postfix seem to me good candidates. There are 6 Courier authdaemond running. Postfix starts 5 saslauthd. Courier has a number of couriertcpd and courierloggers (imap, imap-ssl, pop3, pop3-ssl) Every user that connects via IMAP starts his own processes (gam_server, imapd, couriertls, etc.). Postfix has loads of different little processes like pickup, qmgr, tlsmgr, anvil etc. Apache has 5+5 processes - these are easy to reduce, although I am hesitating to do this too radically. Same applies for the ISPConfig httpd processes. Mailman is a story of itself, starting about 10 python processes for the different tasks its doing. This is the only software that I have installed on top of the ISPConfig/DebianEtch standard system. I wonder if anybody else ever did some sort of process-reduction on his/her server and what the hints might be on where to start and what not to touch. Best idea might be to change the hosting company...! ;-) Thanks for your input on this. Regards, Tom
You should also switch the antivirus to use clamd instaed of clamscan. The ISPconfig httpd is alreayd set to 1 process if I remember correctly.
Hi Till, thanks loads for you lightning fast answer...! ISPConfig: Funny enough there are still three ispconfig_httpd processes running... Yet, this doesn't seem to be the big issue. I think its mainly the mail/imap software that makes things difficult. But anyway: What was the clamd/clamscan thing? Any pointer for that one?
