ChangeLog.txt 5.1 KB

  1. Changes since 2.9
  2. -----------------
  3. * Fixed failure to compile in paths containing spaces.
  4. * Fixed edge case with CreateProcess().
  5. Correctly handle the case where the application executable is under
  6. a path which contains space and an executable sharing the initial
  7. part of that path (up to a space) exists.
  8. Changes since 2.8
  9. -----------------
  10. * Fixed failure to run on Windows versions prior to Vista.
  11. Changes since 2.7
  12. -----------------
  13. * Read Application, AppDirectory and AppParameters before each restart so
  14. a change to any one doesn't require restarting NSSM itself.
  15. * Fixed messages not being sent to the event log correctly in some
  16. cases.
  17. * Try to handle (strictly incorrect) quotes in AppDirectory.
  18. Windows directories aren't allowed to contain quotes so CreateProcess()
  19. will fail if the AppDirectory is quoted. Note that it succeeds even if
  20. Application itself is quoted as the application plus parameters are
  21. interpreted as a command line.
  22. * Fixed failed to write full arguments to AppParameters when
  23. installing a service.
  24. * Throttle restarts.
  25. Back off from restarting the application immediately if it starts
  26. successfully but exits too soon. The default value of "too soon" is
  27. 1500 milliseconds. This can be configured by adding a DWORD value
  28. AppThrottle to the registry.
  29. Handle resume messages from the service console to restart the
  30. application immediately even if it is throttled.
  31. * Try to kill the process tree gracefully.
  32. Before calling TerminateProcess() on all processes assocatiated with
  33. the monitored application, enumerate all windows and threads and
  34. post appropriate messages to them. If the application bothers to
  35. listen for such messages it has a chance to shut itself down gracefully.
  36. Changes since 2.6
  37. -----------------
  38. * Handle missing registry values.
  39. Warn if AppParameters is missing. Warn if AppDirectory is missing or
  40. unset and choose a fallback directory.
  41. First try to find the parent directory of the application. If that
  42. fails, eg because the application path is just "notepad" or something,
  43. start in the Windows directory.
  44. * Kill process tree when stopping service.
  45. Ensure that all child processes of the monitored application are
  46. killed when the service stops by recursing through all running
  47. processes and terminating those whose parent is the application
  48. or one of its descendents.
  49. Changes since 2.5
  50. -----------------
  51. * Removed incorrect ExpandEnvironmentStrings() error.
  52. A log_event() call was inadvertently left in the code causing an error
  53. to be set to the eventlog saying that ExpandEnvironmentStrings() had
  54. failed when it had actually succeeded.
  55. Changes since 2.4
  56. -----------------
  57. * Allow use of REG_EXPAND_SZ values in the registry.
  58. * Don't suicide on exit status 0 by default.
  59. Suiciding when the application exits 0 will cause recovery actions to be
  60. taken. Usually this is inappropriate. Only suicide if there is an
  61. explicit AppExit value for 0 in the registry.
  62. Technically such behaviour could be abused to do something like run a
  63. script after successful completion of a service but in most cases a
  64. suicide is undesirable when no actual failure occurred.
  65. * Don't hang if startup parameters couldn't be determined.
  66. Instead, signal that the service entered the STOPPED state.
  67. Set START_PENDING state prior to actual startup.
  68. Changes since 2.3
  69. -----------------
  70. * Ensure systems recovery actions can happen.
  71. In Windows versions earlier than Vista the service manager would only
  72. consider a service failed (and hence eligible for recovery action) if
  73. the service exited without setting its state to SERVICE_STOPPED, even if
  74. it signalled an error exit code.
  75. In Vista and later the service manager can be configured to treat a
  76. graceful shutdown with error code as a failure but this is not the
  77. default behaviour.
  78. Try to configure the service manager to use the new behaviour when
  79. starting the service so users who set AppExit to Exit can use recovery
  80. actions as expected.
  81. Also recognise the new AppExit option Suicide for use on pre-Vista
  82. systems. When AppExit is Suicide don't stop the service but exit
  83. inelegantly, which should be seen as a failure.
  84. Changes since 2.2
  85. -----------------
  86. * Send properly formatted messages to the event log.
  87. * Fixed truncation of very long path lengths in the registry.
  88. Changes since 2.1
  89. -----------------
  90. * Decide how to handle application exit.
  91. When the service exits with exit code n look in
  92. HKLM\SYSTEM\CurrentControlSet\Services\<service>\Parameters\AppExit\<n>,
  93. falling back to the unnamed value if no such code is listed. Parse the
  94. (string) value of this entry as follows:
  95. Restart: Start the application again (NSSM default).
  96. Ignore: Do nothing (srvany default).
  97. Exit: Stop the service.
  98. Changes since 2.0
  99. -----------------
  100. * Added support for building a 64-bit executable.
  101. * Added project files for newer versions of Visual Studio.