Comments on: Disable CoreDump on Apache with suPHP

By: nopheme

nopheme — Fri, 16 Oct 2009 18:54:47 +0000

Thanks piyecarane, finding a way to change the ulimits was hell.

By: rowan

rowan — Mon, 09 Mar 2009 22:54:23 +0000

Thanks for this! I had a similar problem with suphp dumping core files all over the place

By: Mike

Mike — Mon, 12 Jan 2009 21:31:42 +0000

Hey there,

i tried to set this up – but the rlimitnprocs are ignored by apache.
would you mind to give some more infos about what you actually wrote in the virtual host section?
maybee i think wrong but its still creating way more procs than i set with rlimitnpro.

thanks!

By: Soko banja, Serbia

Soko banja, Serbia — Thu, 11 Dec 2008 13:26:38 +0000

I have a headache with this coredump files. How can edit them to see what’s wrong ???

By: Mo

Mo — Sat, 01 Nov 2008 07:55:26 +0000

if it is not too much to ask, could you please write an article on how to implement this step by step not only to disable codedumps but the whole thing. Also, how to test if our setup is working good and limits are enforced.

I think many people would find this very helpful.

one of our biggest issues in shared hosting is to control CPU and Memory limits per site/user.

thanks in advance.

By: piyecarane

piyecarane — Thu, 09 Oct 2008 07:46:50 +0000

Under suPHP system, I put rlimit for each vhost for example :
RLimitCPU 20 40
RLimitMEM 419430400 419430400
RLimitNPROC 20 30

First limit is soft limit, the second one is hard limit. For RLimitCPU, you can set it start from 1.

By: Mo

Mo — Thu, 18 Sep 2008 22:29:20 +0000

Thanks for the info, very useful.

Could you please explain in more details regarding this:
“After setting up suPHP with rlimit rule per vhosts, I see that Rlimit really works. Apache kills all PHP execution that hit the Rlimit.”

Like, how did you make the settings, in which files, what is the accepted rlimit you put there?

thank you.