On Feb 26, 2010, at 8:35 AM, Nilesh Govindarajan wrote:
> Prefork is always like that. It will spawn a process for each request.
Not exactly. It spawns processes ahead of time, and then manages the process
pool within specified parameters. Saying that it spawns a process for each
request somew
On Feb 26, 2010, at 8:31 AM, Richard Peacock wrote:
> I was diagnosing an un-related issue on my web-server and had to list
> processes to see which PID needed to be killed. I noticed that there were
> several entries for the “http2-prefork” process …
>
> I mean, it’s not a huge problem or a
On Fri, Feb 26, 2010 at 7:01 PM, Richard Peacock <
richard.peac...@minorplanet.com> wrote:
> Hi guys,
>
> I am sorry if this is such a newbie question!
>
>
>
> I was diagnosing an un-related issue on my web-server and had to list
> processes to see which PID needed to be killed. I noticed that t
On Fri, Feb 26, 2010 at 8:31 AM, Richard Peacock
wrote:
> Hi guys,
>
> I am sorry if this is such a newbie question!
>
>
>
> I was diagnosing an un-related issue on my web-server and had to list
> processes to see which PID needed to be killed. I noticed that there were
> several entries for the
Hi guys,
I am sorry if this is such a newbie question!
I was diagnosing an un-related issue on my web-server and had to list
processes to see which PID needed to be killed. I noticed that there
were several entries for the "http2-prefork" process ...
[start]
wwwrun8786 0.0 0.5 88452
