> > Hhhm 120 different daemons instead of 2 or 3? All with minimum 5 child
> > processes? Ickk, I don't claim to be a virtual memory expert, but that
> > sounds like it would load down both the kernel and virtual memory
> > sub-system a little bit... [extra 600 tasks...]
>
> No no not what I meant. You tell apache to bind the main server to one
> address and the other virtual host declarations bind the other addresses.
> It is still one daemon.
ahh... list every IP address in a listen directive, except for the ones I
want to pick up with a different daemon... Skipping the IN_ADDR_ANY
bind...
OK, that will work... A significant change to the config file, and
requiring a little more effort on my part, but it will work. :-)
[for the list archive and search engines: Apache 1.1.1 on 2.0 Linux kernel.
running multiple daemons SO_REUSEADDR -- Under the 2.0 kernel you can't
bind to port 80 on all interfaces, and later start up another process
that listens to a more specific port. The solution is to ONLY bind to
specific addresses. ]
>
> Some other servers (eg netscrap enterprise server) work the way you
> described above.
>
> Alan
>
>
----------------------------------------------------------------------
tbrown@BareMetal.com (604) 598-7708 http://BareMetal.com/
Virtual WWW servers -- Advanced WWW tools & Internet consulting