I am reading from the official openSuse 13.1 reference guide, and hit at least one error. You see, I had installed Apache2 when I first installed OpenSuse 13.1; letting yast do the default configuration and start Apache. All was fine, except I had no SSL. Today, I edited the relevant conf files to enable SSL, and I generated my own CA, and created a server CRT; and put all the rquired key and certificate files in the right places. Now I want to TEST the configuration files as they are now, and reading from the official guide (but my main source of info was http://doc.opensuse.org/products/draft/SLES/SLES-admin_sd_draft/cha.apache2....), I see that I can do that using" rcapache2 configtest Alas, that fails with the message that /etc/init.d/apache2 does not exist. I looked, and it is right. There is no apache2 file in /etc/init.d. I don't know if that is a defect in the documentation or a bug in rcapache2, and I do not care. All I want is to know how I can check the new configuration before risking stopping and trying to restart apache. How do I do this? One other question. I have recently become aware of nginx, and have been reading that it performs much better that apache on limited hardware under heavy load. Can anyone confirm this? Further, will if work with the same document root and cgi-bin directories that apache uses, or does it want it's own? I would like to download the latest nginx (version 1.6 I believe), and install it, but do I have to stop apache before I do so? Ideally, I'd like to be able to switch back and forth between apache2 and nginx, so I can run tests to compare and contrast the two on the same machine. But can I do so without creating major headaches for myself? One of the things I have to check is the behaviour of each in handling optional checking of client side certificates. What I have to investigate is how to have optional checking of client side certificates, for hundreds of pages (and restricting their content if a client side certificate is not present), and making checking of client side certificates mandatory in order for the user to have access to a very small number of pages. I found where/how to make client certificates optional (for Apache2), but not how to make it mandatory for a given page. And I have yet to begin to investigate this for nginx. Any tips would be appreciated. It occurs to me to ask if anyone knows if there is an opensource application server that has the same relation to Tomcat that nginx has to Apache's httpd server (i.e. mature code that performs better on limited hardware under heavy load)? (and no, I am not interested in something imcomplete or only in alpha testing or even beta testing - and I do not have a budget for products that are not open source). Thanks Ted -- R.E.(Ted) Byers, Ph.D.,Ed.D. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org