In history I used apache 1.3 with an oder SUSE distribution.
There I have several httpd processes start for various ports.
This allow to enable/disable some http ports without affecting the others.
(I use https, virtual hosts of course there cannot be two httpd processes for the same port)
Now with the apache 2.0 od SUSE 9.1 it seems, that I cannot start more than one httpd process even when they use different ports.
All I get is the message: "httpd alread running" and the PID of it.
Is there a way to have several ports be dealed independently with apache 2.0?
Of course one httpd daemon is able to provide all ports, but I want to reconfigure e.g. one port (restartng httpd for ist) without affection other https ports.
In other words. When I restart httpd (which takes just seconds I know) to make some change (e.g. disbale a port or enable a new one)
I assume that all sessions to all httpd ports are closed.
For me this means that actual users on other ports which I do not want to touch are kicked out, too. And I don't want this.
The benefit of my historc method to run several httpd processes was, that if one process will hang, the other ports served by other httpd processes are not affected. This is a kind of redundency.
So is there a way to start apache 2.0 several times for different ports or is there a method to enable/add or disable one specific https port without affecting the other ones?
Any comments are welcome
how bout make your changes and then do the restart at night when probably no one will get kicked off
Thank you for your tip.
This is just a partial workaround.
Some changes shoud be done immediately and this solve not the point of redundancy and independency of different ports.
By the way: What happens with open browser windows/sessions when the webserver is restarted? (I sould make this experiment....)
the big issue is that your probably running httpd from xintd or inid, they are what will not let you start more than one (most likely, ive never tried) but its not really an issue, Virtual Hosting will let you serve apache on multiple ports, but in the time it takes httpd to restart, most client wont even have resend the request data, only very basic clients (like telnet) would notice, unless someone was activly downloading a page, but even then, it would regester as a timeout and the browser would re-request the data, and your server would probably be back up by that point. partialy dependent on the speed of your machine, but its not going to be a major problem in the second that you reboot the process unless your handling like 20-30 outgoing at a time.