Marco A. Zamora Cunningham wrote:
   Secure0: SSLMutex  file:/var/cache/apache2-mod_ssl/ssl_mutex0
   Secure1: SSLMutex  file:/var/cache/apache2-mod_ssl/ssl_mutex1
This way I can avoid collisions between the two independant apache 
servers running modssl and avoid mutex problems?  My understanding is 
    

Off the top of my head, I'd say this won't work: the mutexes are for the SSL
cache updates, so: since all virtual servers are really running in the same
pool of Apache httpd processes, they all need access to the same mutexes.
Furthermore, maybe some of the the modssl functions/libraries assume that
all modssl processes use the same shared memory/files/whatever.

So, in order to check if your setup works, I'd first set up each virtual
server as an actual server (each IP with its own set of httpd processes and
independent configs using -D switches and ifdefs), and then I'd try
segregating the mutexes, and until that is done, I'd run an SSL connection
  
Perhaps you missed this?  I did setup each IP with it's own httpd server, here is the 'pstree -cp':

        |-httpd2(3397)-+-advxsplitlogfil(3404)
        |              |-httpd2(3405)
        |              |-httpd2(3406)
        |              |-httpd2(3407)
        |              |-httpd2(3408)
        |              |-httpd2(3409)
        |              `-httpd2(3450)
        |-httpd2(3415)-+-advxsplitlogfil(3422)
        |              |-httpd2(3423)
        |              |-httpd2(3424)
        |              |-httpd2(3425)
        |              |-httpd2(3426)
        |              `-httpd2(3427)
        |-httpd2(3433)-+-advxsplitlogfil(3440)
        |              |-httpd2(3441)
        |              |-httpd2(3442)
        |              |-httpd2(3443)
        |              |-httpd2(3444)
        |              `-httpd2(3445)


And from 'netstat -apn' snippet:

tcp        0      0 64.179.36.99:80         0.0.0.0:*               LISTEN      3397/httpd2
tcp        0      0 64.179.36.101:443       0.0.0.0:*               LISTEN      3433/httpd2
tcp        0      0 64.179.36.100:443       0.0.0.0:*               LISTEN      3415/httpd2



The goal was to stack three ip addresses into one box, then attach an httpd server to each of the ip's.  One name based http server and two IP based https servers.  This we have, only I wonder if the SSLMutex designation should point to unique filenames or must it be a file that is common to all three httpd servers?

Regards,

TomW

-- 
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net, http://cyberiansoftware.com
"Windows? No thanks, I have work to do..."
----------------------------------------------------

Reply via email to