X-Git-Url: http://git.iain.cx/?a=blobdiff_plain;f=README.txt;h=1bf8ab9ac90ca370bd7cf391be72576374934341;hb=ba3c81e07740130a415c62680bc571b2d8bb5aec;hp=88a729078321e1469a9a4a68a6efe9d1588915ff;hpb=70453ecb690ff5d6008677ced1016d0235bee329;p=nssm.git

diff --git a/README.txt b/README.txt
index 88a7290..1bf8ab9 100644
--- a/README.txt
+++ b/README.txt
@@ -72,11 +72,12 @@ 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.
 
 NSSM will look in the registry under
 HKLM\SYSTEM\CurrentControlSet\Services\<service>\Parameters\AppExit for