NSSM: The Non-Sucking Service Manager\r
-Version 2.6, 2010-11-19\r
+Version 2.7, 2011-01-25\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
\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 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
\r
NSSM will look in the registry under\r
HKLM\SYSTEM\CurrentControlSet\Services\<service>\Parameters\AppExit for\r
Thanks to Bernard Loh for finding a bug with service recovery.\r
Thanks to Benjamin Mayrargue (www.softlion.com) for adding 64-bit support.\r
Thanks to Joel Reingold for spotting a command line truncation bug.\r
+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