Hi Nick, of course does it make sense to me.
Why would I want to have 10 preforked httpd children listening on 192.168.*.*:80 when I know that there will be only occassional single requests to this private address. As I said this URL should only server internal occassional maintenance and stats requests. # lsof -ni tcp:80,443|grep -c LIST 33 # lsof -ni tcp:80,443|grep -c 192\.168 11 Wouldn't you agree that the memory footprint (let alone TCP buffers and (idle) processing) thus is unecessarily wasteful? # ps -C httpd -o comm,vsz COMMAND VSZ httpd 10124 httpd 10260 httpd 10260 httpd 10260 httpd 10260 httpd 10260 httpd 10260 httpd 10408 httpd 10260 httpd 10352 httpd 10260 > -----Original Message----- > From: Nick Kew [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 01, 2006 3:21 PM > To: users@httpd.apache.org > Subject: Re: [EMAIL PROTECTED] Why doesn't Apache bind socket to > vhost's IP > addr.? > > > On Wednesday 01 March 2006 13:39, [EMAIL PROTECTED] wrote: > > > Is there a way to restrict the forked servers for this vhost > > while keeping the higher numbers for the public webserver? > > That doesn't make sense. None of your children are "for" either > this vhost or the public webserver; they just serve whatever requests > they receive. > > -- > Nick Kew > > ----------------------------------------------------------------- ---- > The official User-To-User support forum of the Apache HTTP > Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: [EMAIL PROTECTED] > " from the digest: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
