X-Git-Url: http://git.iain.cx/?a=blobdiff_plain;f=README.txt;h=c9cd2cd6bca39213272aa7905de318346742de52;hb=747b6768e1f97a89dda651c1b4a4a7a4df9c206d;hp=88a729078321e1469a9a4a68a6efe9d1588915ff;hpb=63363fbc93ec23e1673113029e819c1a55dd7967;p=nssm.git

diff --git a/README.txt b/README.txt
index 88a7290..c9cd2cd 100644
--- a/README.txt
+++ b/README.txt
@@ -1,5 +1,5 @@
 NSSM: The Non-Sucking Service Manager
-Version 2.7, 2011-01-25
+Version 2.11, 2012-04-04
 
 NSSM is a service helper program similar to srvany and cygrunsrv.  It can 
 start any application as an NT service and will restart the service if it 
@@ -9,7 +9,7 @@ NSSM also has a graphical service installer and remover.
 
 Full documentation can be found online at
 
-                           http://iain.cx/src/nssm/
+                              http://nssm.cc/
 
 Since version 2.0, the GUI can be bypassed by entering all appropriate 
 options on the command line.
@@ -24,6 +24,11 @@ Since version 2.3, NSSM logs to the Windows event log more elegantly.
 
 Since version 2.5, NSSM respects environment variables in its parameters.
 
+Since version 2.8, NSSM tries harder to shut down the managed application
+gracefully and throttles restart attempts if the application doesn't run
+for a minimum amount of time.
+
+Since version 2.11, NSSM respects srvany's AppEnvironment parameter.
 
 Usage
 -----
@@ -72,11 +77,17 @@ keep trying, pausing between each attempt, until the service is successfully
 started or you send it a stop signal.
 
 NSSM will pause an increasingly longer time between subsequent restart attempts
-if the service fails to start in a timely manner, up to a maximum of 60 seconds.
-This is so it does not consume an excessive amount of CPU time trying to start
-a failed application over and over again.  If you identify the cause of the
-failure and don't want to wait you can use the Windows service console to
-send a continue signal to NSSM and it will retry within a few seconds.
+if the service fails to start in a timely manner, up to a maximum of four
+minutes.  This is so it does not consume an excessive amount of CPU time trying
+to start a failed application over and over again.  If you identify the cause
+of the failure and don't want to wait you can use the Windows service console
+(where the service will be shown in Paused state) to send a continue signal to
+NSSM and it will retry within a few seconds.
+
+By default, NSSM defines "a timely manner" to be within 1500 milliseconds.
+You can change the threshold for the service by setting the number of
+milliseconds as a REG_DWORD value in the registry at
+HKLM\SYSTEM\CurrentControlSet\Services\<service>\Parameters\AppThrottle.
 
 NSSM will look in the registry under
 HKLM\SYSTEM\CurrentControlSet\Services\<service>\Parameters\AppExit for
@@ -159,6 +170,9 @@ Building NSSM from source
 NSSM is known to compile with Visual Studio 6, Visual Studio 2005 and Visual
 Studio 2008.
 
+NSSM will also compile with Visual Studio 2010 but the resulting executable
+will not run on versions of Windows older than XP SP2.
+
 
 Credits
 -------
@@ -168,7 +182,12 @@ Thanks to Joel Reingold for spotting a command line truncation bug.
 Thanks to Arve Knudsen for spotting that child processes of the monitored
 application could be left running on service shutdown, and that a missing
 registry value for AppDirectory confused NSSM.
-Thanks to Peter Wagemans and Laszlo Kereszt for suggesting throttling restarts.
+Thanks to Peter Wagemans and Laszlo Keresztfalvi for suggesting throttling restarts.
+Thanks to Eugene Lifshitz for finding an edge case in CreateProcess() and for
+advising how to build messages.mc correctly in paths containing spaces.
+Thanks to Rob Sharp for pointing out that NSSM did not respect the
+AppEnvironment registry value used by srvany.
+Thanks to Szymon Nowak for help with Windows 2000 compatibility.
 
 Licence
 -------