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!
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.
I had a couple of consultants install Subversion on our servers to help us keep track of some running projects. Little did i know that Subversion installed the apache httpd ver 2.0, which I DO NOT want to use, which brings me to my issue:
simply typing HTTPD on my system, the server thinks I am talking about the ver 2.0 of apache, not the version I want to use. This carries through with cPanel, so anytime cpanel does anything with apache - it does so with the ver 2.0 that was installed with subversion.
How do I change the systems understanding of the command "httpd" so it points to another version of apache?
is that some sort of environment variable?
No, it's not an environment variable, it's how the elements in root's $PATH are searched for matching items. Say the PATH is set to "/bin:/usr/local/bin", now if you have a binary "httpd" in both directories the one in /bin would be found first. You can see and test that typing "which -a httpd". About Cpanel/WHM I don't know, maybe it could work if you explicitly set the PATH in it's startup script to how you want it.
When you type which httpd the system will tell you which one it is using. Suppose the output is /bin/httpd, and this is the apache version 2.0 that you do not want to use.
Can't you just rename /bin/httpd to something else and then make a symlink so /bin/httpd points to the version you do want to use? Or am I missing something blindingly obvious here?
Distribution: Red Hat (8.0, RHEL5,6), CentOS, SuSE (10.x, 11.x, 12.2, 13.2), Solaris (8-10), Tru64, MacOS, Raspian
Originally Posted by unSpawn
How would you manage the 2.0 httpd then?
Well, you could set up an account to "own" and manage the Apache 2.x" software and modify it's PATH to find the Apache 2 binaries. Also, you'd probably want to tweak a bunch of settings in the configuration file(s) so that the two versions kept log files and such in separate directories. Yuk.