ZT from Nginx official site.
Known Issues
Possible Future Enhancements
Version of Nginx for Windows uses the native Win32 API (not the Cygwin emulation layer). Only select()
the connection processing method was currently used, so high performance and scalability should isn't be expected. Due to the and some other known issues version of the Nginx for Windows are considered to bes a beta version. At this time, it provides almost the same functionality as a UNIX version of Nginx except for XSLT filter, image filter, G EoIP module, and embedded Perl language.
To install nginx/windows, download the latest development version distribution (1.3.4), since the development branch of NG Inx contains all known fixes. Then unpack the distribution, Go to the nginx-1.3.4 directory, and run nginx
. Example for the C:root directory:
CD C:unzip NGINX-1.3.4.ZIPCD Nginx-1.3.4start nginx
Run the tasklist
command-line utility to see Nginx processes:
C:\nginx-1.3.4>tasklist/fi "imagename eq nginx.exe" Image name PID Session name session# Mem usage===== ========== ======== ============== ========== ============nginx.exe 652 Console 0 2 780 Knginx.exe 1332 Console 0 3 (K)
One of the processes is the master process and another are the worker process. If Nginx does not start, look for the reason in the error log file logs\error.log
. If The log file has no been created, the reason for this should is reported in the Windows Event log. If An error page was displayed instead of the expected page, also look for the reason in the logs\error.log
file.
Nginx/windows uses the directory where it has been run as the prefix for relative paths in the configuration. In the example above, the prefix is C:\nginx-1.3.4\
. Paths in a configuration file must is specified in Unix-style using forward slashes:
Access_log logs/site.log;root c:/web/html;
Nginx/windows runs as a standard console application (not a service), and it can be managed using the following commands:
Nginx-s stop |
Fast Shutdown |
Nginx-s quit |
Graceful shutdown |
Nginx-s Reload |
Changing configuration, starting new worker processes with a new configuration, graceful shutdown of the old worker processes |
Nginx-s Reopen |
Re-opening log files |
Known Issues
- Although several workers can be started, and only one of the them actually does any work.
- A worker can handle no more than 1024x768 simultaneous connections.
- The cache and other modules which require shared memory support does not work in Windows Vista and later versions due to add Ress space layout randomization being enabled in these Windows versions.
Possible Future Enhancements
- Running as a service.
- Using the I/O completion ports as a connection processing method.
- Using multiple worker threads inside a single worker process.
Nginx for Windows