Matt wrote:
...
No, that would be a painful way to do things...and it wouldn't fix
your problem, as both instances would bind to the IP, port and config
files by default.
Just did this yesterday myself, in fact, so I'm suddenly an "expert" :)
(i.e., wait a bit for people to tell you how wrong I am!)
httpd can be run multiple times with multiple configs, just configure
it to use different ports/IPs, and run each with a different config.
Copy your httpd.conf file to another name.
Configure it as you wish, changing the port/IP address as appropriate.
run it as "httpd -f /var/www/conf/2ndhttpd.conf". ta-da!
I used this to run a second copy of httpd which was running as a user
which DID have write privileges to the html documents directory. This
second instance is running on a different port. I then used pf to
redirect CERTAIN external IP addresses to that second port, so now
some locations on the Internet get one instance, the rest get the
primary instance.
Nick.
| Andrew Morton | -mm merge plans for 2.6.23 |
| Benjamin Herrenschmidt | Re: [PATCH] Remove process freezer from suspend to RAM pathway |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Mel Gorman | [PATCH 6/8] x86_64 - Specify amount of kernel memory at boot time |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Jarek Poplawski | Re: Soft-Lockup/Race in networking in 2.6.31-rc1+195 ( possibly?caused by netem) |
