Apache bug on Windows XP SP2

Apache 1.3.x 2.0.x 2.2.x has bugs in Windows XP SP2. The following is a Web article, but I have verified that this method is sometimes not easy to use. At least it is not easy for me to use, it is also SP2, and another machine can be used, which is really depressing. Isn't it forced us to use IIS ??

* Author: galun @ Internet, from: http://www.gallonwang.com reprint please note the source name

Recently I have prepared several PHP websites, so I need to install a PHP server on my computer. I haven't touched PHP, Apache for a long time, when MySQL is used, you just need to steal the lazy package and call it appserv. It can install PHP, MySQL, Apache, Zend, and phpMyAdmin software on your machine at one time, it is very convenient, and there are multiple combinations of methods, you can go to his website for details. because I used this software a long time ago, it can be used after it is installed like the software, but this time it has encountered a big problem. I downloaded it first.
Appserv 2.5.3. My system is Windows XP SP2.
# PHP 5.0.3
# Apache 2.0.52
# MySQL 4.1.8
# Zend optimizer 2.5.7
# PhpMyAdmin 2.6.1-RC2
After the installation, we found that the hard drive lights were flashing, and the computer was very slow. it cannot be used normally. we can see that there are two Apache processes, one of which is jumping out from time to occupy a large amount of CPU resources, and there is no way to force stop them. we thought it was a conflict between apache2.0 and the XP system, and we downloaded appserv 2.4.3 again.
# PHP 4.3.10
# Apache 1.3.33
# MySQL 4.1.8
# Zend optimizer 2.5.7
# PhpMyAdmin 2.6.1-RC2
After installation, Apache cannot be started at all. view the log file display.
Error. log:
[Sat Aug 06 22:47:12 2005] [crit] (10022) provides an invalid parameter. : Setup_inherited_listeners: wsasocket failed to open the inherited socket.
So I googled and found an article "solution to failure of Apache to work under Win [SP2"
Http://blog.chinaunix.net/article... 36486 & blogid = 8054 reference
Apache SP2 starts CPU setup_inherited_listeners

System: Windows [SP2]
-----------------------------------------------
Software: Apache 1.3 *
Symptom: the service cannot be started. In the Service Startup report, "The service is automatically disabled after it is started..."
Errlog:
[Mon Jul 18 12:48:24 2005] [crit] (10022) provides an invalid parameter. : Setup_inherited_listeners: wsasocket failed to open the inherited socket.
Bytes -------------------------------------------------------------------------------------------------------------
Software: Apache 2.0 .*
Symptom: It can be started normally, but it occupies a lot of CPU and does not release the memory. (because you have been trying to run sub-processes, you can see two Apache processes frequently in the task manager.) access with 127.0.0.1 does not respond.
Errlog:
[Mon Jul 18 04:07:28 2005] [Notice] server built: Feb 10 2005 06:11:34
[Mon Jul 18 04:07:28 2005] [Notice] parent: created child process 448
[Mon Jul 18 04:07:28 2005] [Notice] child 448: child process is running
[Mon Jul 18 04: 2005] [crit] (OS 10022) provides an invalid parameter. : Child 448: setup_inherited_listeners (), wsasocket failed to open the inherited socket.
[Mon Jul 18 04:07:28 2005] [Error] parent: child process exited with status 3 -- aborting.
[Mon Jul 18 04:07:29 2005] [Notice] Apache/2.0.53 (win32) configured -- resuming normal
========================================================== ====================================
Resolution:
1. Network neighbors-local connection-properties-advanced-wins tags-remove the check box before enabling LmHosts query.
Alternatively, choose "Control Panel"> "Windows Firewall"> "Advanced tab"> "network connection settings"> "Settings", select the "Secure Web Server (https)" option, and press "OK" twice.
++
As he said, according to the Operations he knows, he found that the path of the solution provided by him is completely wrong. No wonder many people reply that they cannot find the WINS tag. the correct path found through my practice is posted below.
Correct Solution
1. Select "Network Neighbor"> "Local Connection"> "properties"> "Internet Protocol" (TCP/IP)> "properties"> "advanced"> "wins tag"> remove the check box before enabling the LmHosts query.
2. Select "Control Panel"> "Windows Firewall"> "Advanced tab"> "local connection settings"> "service", and select "Secure Web Server (https ..

In this way, the problem is completely solved, and my Apache server can be used normally. I hope to give you some reference.