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=10192>. 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=10192 Unable to debug configeration file due to change in apche 2.0 or above Summary: Unable to debug configeration file due to change in apche 2.0 or above Product: Apache httpd-2.0 Version: 2.0.39 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: Other Component: All AssignedTo: bugs@httpd.apache.org ReportedBy: [EMAIL PROTECTED] The 2.0 serise of apache for win 32 is quite impressive, however their is a small bug that needs to be addressed. During the incorprotation of the apache monitor the test configeration commands restart, stop and start apache have changed. They no longer wait for 20 seconds so that any valuable debuging infomation is displayed. Is their a command that can be passed to apache to wait for 20 seconds in this circumstance or do i have to try and use cmd.exe or ms dos, which wouldn't work anyway. This is because it is compiled for win 32 and wilnot run on dos. This seems quite silly but trying to hit the brake key at 12 o'clock in the evening is not the easist of things. Especily just to find out that i foregot to uncomment the end of the proxy module directive. Don't laugh it's quite hard to do this sort of thing that late in the evening. Anyway this needs to be sorted somehow. I would of thought that the apache toolbox would come up with error messages if the configeration is incorrect. Is that just too obvious? Little things like this could help make apache a viable alternative! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]