Messages for kill_process_tree().

[nssm.git] / README.txt

diff --git a/README.txt b/README.txt
index 022e5ed..ecc59e0 100644 (file)
--- a/README.txt
+++ b/README.txt
@@ -1,5 +1,5 @@
 NSSM: The Non-Sucking Service Manager\r
-Version 2.4, 2010-09-23\r
+Version 2.6, 2010-11-19\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
@@ -22,6 +22,8 @@ based on the exit code of the managed application.
 \r
 Since version 2.3, NSSM logs to the Windows event log more elegantly.\r
 \r
+Since version 2.5, NSSM respects environment variables in its parameters.\r
+\r
 \r
 Usage\r
 -----\r
@@ -71,7 +73,7 @@ successfully started or you send it a stop signal.
 \r
 NSSM will look in the registry under\r
 HKLM\SYSTEM\CurrentControlSet\Services\<service>\Parameters\AppExit for\r
-string (REG_SZ) values corresponding to the exit code of the application.\r
+string (REG_EXPAND_SZ) values corresponding to the exit code of the application.\r
 If the application exited with code 1, for instance, NSSM will look for a\r
 string value under AppExit called "1" or, if it does not find it, will\r
 fall back to the AppExit (Default) value.  You can find out the exit code\r
@@ -97,7 +99,10 @@ of Windows you should use "Suicide" instead.
 \r
 If the value data is "Suicide" NSSM will simulate a crash and exit without\r
 informing the service manager.  This option should only be used for\r
-pre-Vista systems where you wish to apply a service recovery action.\r
+pre-Vista systems where you wish to apply a service recovery action.  Note\r
+that if the monitored application exits with code 0, NSSM will only honour a\r
+request to suicide if you explicitly configure a registry key for exit code 0.\r
+If only the default action is set to Suicide NSSM will instead exit gracefully.\r
 \r
 \r
 Removing services using the GUI\r