Fix pre-Vista compatibility.

[nssm.git] / README.txt

diff --git a/README.txt b/README.txt
index 88a7290..b2f9c27 100644 (file)
--- a/README.txt
+++ b/README.txt
@@ -1,5 +1,5 @@
 NSSM: The Non-Sucking Service Manager\r
-Version 2.7, 2011-01-25\r
+Version 2.8, 2011-02-26\r
 \r
 NSSM is a service helper program similar to srvany and cygrunsrv.  It can \r
 start any application as an NT service and will restart the service if it \r
@@ -24,6 +24,9 @@ Since version 2.3, NSSM logs to the Windows event log more elegantly.
 \r
 Since version 2.5, NSSM respects environment variables in its parameters.\r
 \r
+Since version 2.8, NSSM tries harder to shut down the managed application\r
+gracefully and throttles restart attempts if the application doesn't run\r
+for a minimum amount of time.\r
 \r
 Usage\r
 -----\r
@@ -72,11 +75,17 @@ keep trying, pausing between each attempt, until the service is successfully
 started or you send it a stop signal.\r
 \r
 NSSM will pause an increasingly longer time between subsequent restart attempts\r
-if the service fails to start in a timely manner, up to a maximum of 60 seconds.\r
-This is so it does not consume an excessive amount of CPU time trying to start\r
-a failed application over and over again.  If you identify the cause of the\r
-failure and don't want to wait you can use the Windows service console to\r
-send a continue signal to NSSM and it will retry within a few seconds.\r
+if the service fails to start in a timely manner, up to a maximum of four\r
+minutes.  This is so it does not consume an excessive amount of CPU time trying\r
+to start a failed application over and over again.  If you identify the cause\r
+of the failure and don't want to wait you can use the Windows service console\r
+(where the service will be shown in Paused state) to send a continue signal to\r
+NSSM and it will retry within a few seconds.\r
+\r
+By default, NSSM defines "a timely manner" to be within 1500 milliseconds.\r
+You can change the threshold for the service by setting the number of\r
+milliseconds as a REG_DWORD value in the registry at\r
+HKLM\SYSTEM\CurrentControlSet\Services\<service>\Parameters\AppThrottle.\r
 \r
 NSSM will look in the registry under\r
 HKLM\SYSTEM\CurrentControlSet\Services\<service>\Parameters\AppExit for\r
@@ -168,7 +177,7 @@ Thanks to Joel Reingold for spotting a command line truncation bug.
 Thanks to Arve Knudsen for spotting that child processes of the monitored\r
 application could be left running on service shutdown, and that a missing\r
 registry value for AppDirectory confused NSSM.\r
-Thanks to Peter Wagemans and Laszlo Kereszt for suggesting throttling restarts.\r
+Thanks to Peter Wagemans and Laszlo Keresztfalvi for suggesting throttling restarts.\r
 \r
 Licence\r
 -------\r