httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 39973] New: - Nix on compiled-in paths
Date Thu, 06 Jul 2006 02:36:22 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39973>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39973

           Summary: Nix on compiled-in paths
           Product: Apache httpd-2
           Version: 2.3-HEAD
          Platform: All
               URL: http://httpd.apache.org/docs/2.2/programs/apachectl.html
        OS/Version: All
            Status: NEW
          Severity: major
          Priority: P2
         Component: All
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: Dave@Yost.com


Say apache-2.1.0 is running in /var/apache/. Now I want to build 2.2.2 and try it out using
port 8080.

In the apache-2.2.2 src dir, I run
  configure --prefix=/var/apacheTest
so I won't clobber the running server, and I tweak the /var/apacheTest dir with a new httpd.conf
file 
and maybe some symlinks to the live htdocs dir etc.

There are two problems with this approach:
1. I have to build a special version of php etc. for the /var/apacheTest location.
2. When I decide it's OK to cut over to 2.2.2, I have to re-configure and rebuild apache-2.2.2,
php, etc. 
and take the server down while make install is clobbering things in /var/apache.

It seems to me that the solution is for apachectl to work like this:
  apachectl start [ <apache-root-dir> ]
The only file that should maybe have an apache-root-dir path burned into it is apachectl itself,
so it can 
default to the standard location.  But on unix even that is unnecessary because it is possible
to deduce 
the dir from which apachectl was executed by looking at argv[0].

All pathnames used in conf files and used by modules should normally be relative to apache-root-dir

(whether it was given explicitly or defaulted to).  If you want to put stuff outside of the
apache-root-dir 
tree, you can use full paths in conf files or you can use symlinks on platforms that support
them.

Or something like that.  Forgive me if I am missing something obvious.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message