Removed some legacy stuff.

[nssm.git] / README.txt

diff --git a/README.txt b/README.txt
index 3ef6005..1bf8ab9 100644 (file)
--- a/README.txt
+++ b/README.txt
@@ -68,8 +68,16 @@ action if/when the application dies.
 \r
 With no configuration from you, NSSM will try to restart itself if it notices\r
 that the application died but you didn't send it a stop signal.  NSSM will\r
-keep trying, pausing 30 seconds between each attempt, until the service is\r
-successfully started or you send it a stop signal.\r
+keep trying, pausing between each attempt, until the service is successfully\r
+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 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
 NSSM will look in the registry under\r
 HKLM\SYSTEM\CurrentControlSet\Services\<service>\Parameters\AppExit for\r
@@ -161,6 +169,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
 \r
 Licence\r
 -------\r