DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9614>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9614 Drive letter issues with Apache 2.0.36 Win32 and DocumentRoot... Summary: Drive letter issues with Apache 2.0.36 Win32 and DocumentRoot... Product: Apache httpd-2.0 Version: 2.0.36 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Runtime Config AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] First off, I would like to say that this issue did not appear in 2.0.35 (which I am currently using on another machine). The problem: I have Apache installed on the C drive of my machine (Win2k Professional system with two physical hard disk drives). The web files (.html, .pl, images, etc.) of the web sites are located on the D drive. Any DocumentRoot or <Directory> that is on the D drive will make Apache fail to start (in /logs/error.log, it says "DocumentRoot must be a directory"). An example of what is currently working on Apache 2.0.35 in this configuration but not in 2.0.36 is the following: DocumentRoot "D:/Apache Web Sites/default/inet_pub" - later in httpd.conf - <Directory "D:/Apache Web Sites/default/inet_pub"> (That is in the 'Main' Server Configuration Section of the http.conf file, it also doesn't work in any Virtual Hosts) If I copy the files to the C drive and change the conf file to look like this it will start just fine: DocumentRoot "C:/Apache Web Sites/default/inet_pub" - later in httpd.conf - <Directory "C:/Apache Web Sites/default/inet_pub"> I have narrowed it down to the drive letter causing the problems after extensive trial and error. I even tried mounting the drive currently mounted as "D" to a directory on C called "D-Drive" to see if it worked that way. It did not, so it has something to do with it physically BEING another drive. That, however, shouldn't be a necessary solution to this... especially considering that it worked just fine in all previous versions of Apache I have run on these systems (1.3.22, 1.3.24, 2.0.28 (beta), and 2.0.35). I also tried to put Drive D in the path (a long shot, but just to see if it would work, and THAT didn't work either). Do you have any cleaner ideas than re-mounting my drives (which did NOT work) on how to get this to work the way it used to on Apache Win32 2.0.35? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
