Running a script under mod_perl can be a confusing world to learn about.
The point of mod_perl is that it's a Perl interpreter baked into the Apache web server. Instead of having to run the script (and therefore Perl) every time there's a web request, mod_perl loads the script in a ready-to-run form, so as to improve performance.
Falling back to food analogies (because they're easy for me), it's a bit like a diner making up a batch of pancake batter and having the griddle hot, so that when a customer shows up, the batter can go right onto the hot grill, and pancakes are up five minutes later. The alternative would be to make individual batches of batter for each customer who orders pancakes. I think you can imagine that's not as efficient.
Your experimental results show that Apache is dispatching a request to a variety of kids (diner kitchens), identified by pid. Each request is served (from that kitchen), showing a monotonically increasing count (pancake order count). You should be aware that there's a configuration parameter in the Apache config called something like MaxRequests. When a kid has maxed out its number of requests (that kitchen ran out of batter), it's terminated and a new kid is created (the kitchen makes up a new batch of batter).
Are you just seeing how it all works, or is there some issue that remains a mystery to you? mod_perl has been around for quite a while, but these days I'd guess it's now classified as old technology. :)
In reply to Re: mod_perl children process
by talexb
in thread mod_perl children process
by LorCo
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |