Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm doing name-based IP addresses, and multiple daemons. I already have an apache server working. (this is a production machine.) rather than downloading and compiling apache again, is there some core apache file that I can just find already on the machine, copy it, and create a new instance of apache?
I'm doing name-based IP addresses, and multiple daemons. I already have an apache server working. (this is a production machine.) rather than downloading and compiling apache again, is there some core apache file that I can just find already on the machine, copy it, and create a new instance of apache?
Thank you. B
I don't think you can run multiple instances of apache on one machine. However, you can configure apache to use name-based or ip-based hosting.
"Create a separate httpd installation for each virtual host. For each installation, use the Listen directive in the configuration file to select which IP address (or virtual host) that daemon services. e.g.
Doesn’t that just mean that you need to specify a different configuration file using the -f option for each httpd daemon you start?
From man httpd:
Quote:
-f config
Uses the directives in the file config on startup. If config does not begin
with a /, then it is taken to be a path relative to the ServerRoot. The
default is conf/httpd.conf.
I’ve only used a single httpd daemon for virtual hosting, so I have no practical experience with multiple httpd daemons. There seem to be several down sides to using multiple daemons.
doing an intranet and another public website in addition to the SSL-enabled public website that's already up and running. So, the SSL and the intranet is why i'm thinking of doing it this way.
i'll look into what you are talking about with the man page.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.