RESOLVED WONTFIX 76933
NRWT fails to launch/kill Apache for Apple's Windows port 
https://bugs.webkit.org/show_bug.cgi?id=76933
Summary NRWT fails to launch/kill Apache for Apple's Windows port
Adam Roben (:aroben)
Reported 2012-01-24 12:59:04 PST
NRWT doesn't seem to be able to launch or kill Apache for Apple's Windows port. I believe there are at least two problems: 1) We use Apache 1.x, which doesn't support the "-k start"/"-k stop" options to apachectl 2) Our copy of Apache doesn't support SSL
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2012-01-24 12:59:26 PST
<rdar://problem/10747576>
Dirk Pranke
Comment 2 2012-07-17 17:56:16 PDT
looking at this now, and (as noted in an email) ... I don't actually know where to get a copy of apache for this cygwin config , so this'll be hard to fix :).
Brent Fulgham
Comment 3 2013-05-23 09:55:42 PDT
There seems to be a number of problems with Cygwin and Apache. Cygwin no longer ships Apache 1, and I cannot get the current build of Apache 2.2 that they distribute to run under Windows 7 or Windows 8. The lighttpd program seems to work properly, and starts up and shuts down cleanly under Cygwin. This seems like a better options, especially since this is how Blink is doing things. I briefly attempted to use the stock Apache Foundation's Windows build, but this was even more trouble: The PID generated by the program was a Windows PID (not a Cygwin PID), so the Cygwin kill logic did not properly stop the program. Even after writing conversion logic to get the Cygwin PID from the Windows PID, I found that Apache forks on Windows (creating at least two processes), only one of which is visible to Cygwin. Disaster! I am switching the Apple Windows port to lighttpd.
Brent Fulgham
Comment 4 2013-05-29 14:40:55 PDT
Apache on Cygwin does not seem usable at present. Closing this bug and switching over to lighttpd.
Note You need to log in before you can comment on or make changes to this bug.