3 * Fixed default GUI language being French not English.
7 * Fixed failure to run on Windows 2000.
11 * NSSM is now translated into French.
13 * Really ensure systems recovery actions can happen.
15 The change supposedly introduced in v2.4 to allow service recovery
16 actions to be activated when the application exits gracefully with
17 a non-zero error code didn't actually work.
21 * Support AppEnvironment for compatibility with srvany.
25 * Fixed failure to compile messages.mc in paths containing spaces.
27 * Fixed edge case with CreateProcess().
29 Correctly handle the case where the application executable is under
30 a path which contains space and an executable sharing the initial
31 part of that path (up to a space) exists.
35 * Fixed failure to run on Windows versions prior to Vista.
39 * Read Application, AppDirectory and AppParameters before each restart so
40 a change to any one doesn't require restarting NSSM itself.
42 * Fixed messages not being sent to the event log correctly in some
45 * Try to handle (strictly incorrect) quotes in AppDirectory.
47 Windows directories aren't allowed to contain quotes so CreateProcess()
48 will fail if the AppDirectory is quoted. Note that it succeeds even if
49 Application itself is quoted as the application plus parameters are
50 interpreted as a command line.
52 * Fixed failed to write full arguments to AppParameters when
57 Back off from restarting the application immediately if it starts
58 successfully but exits too soon. The default value of "too soon" is
59 1500 milliseconds. This can be configured by adding a DWORD value
60 AppThrottle to the registry.
62 Handle resume messages from the service console to restart the
63 application immediately even if it is throttled.
65 * Try to kill the process tree gracefully.
67 Before calling TerminateProcess() on all processes assocatiated with
68 the monitored application, enumerate all windows and threads and
69 post appropriate messages to them. If the application bothers to
70 listen for such messages it has a chance to shut itself down gracefully.
74 * Handle missing registry values.
76 Warn if AppParameters is missing. Warn if AppDirectory is missing or
77 unset and choose a fallback directory.
78 First try to find the parent directory of the application. If that
79 fails, eg because the application path is just "notepad" or something,
80 start in the Windows directory.
82 * Kill process tree when stopping service.
84 Ensure that all child processes of the monitored application are
85 killed when the service stops by recursing through all running
86 processes and terminating those whose parent is the application
87 or one of its descendents.
91 * Removed incorrect ExpandEnvironmentStrings() error.
93 A log_event() call was inadvertently left in the code causing an error
94 to be set to the eventlog saying that ExpandEnvironmentStrings() had
95 failed when it had actually succeeded.
99 * Allow use of REG_EXPAND_SZ values in the registry.
101 * Don't suicide on exit status 0 by default.
103 Suiciding when the application exits 0 will cause recovery actions to be
104 taken. Usually this is inappropriate. Only suicide if there is an
105 explicit AppExit value for 0 in the registry.
107 Technically such behaviour could be abused to do something like run a
108 script after successful completion of a service but in most cases a
109 suicide is undesirable when no actual failure occurred.
111 * Don't hang if startup parameters couldn't be determined.
112 Instead, signal that the service entered the STOPPED state.
113 Set START_PENDING state prior to actual startup.
117 * Ensure systems recovery actions can happen.
119 In Windows versions earlier than Vista the service manager would only
120 consider a service failed (and hence eligible for recovery action) if
121 the service exited without setting its state to SERVICE_STOPPED, even if
122 it signalled an error exit code.
123 In Vista and later the service manager can be configured to treat a
124 graceful shutdown with error code as a failure but this is not the
127 Try to configure the service manager to use the new behaviour when
128 starting the service so users who set AppExit to Exit can use recovery
131 Also recognise the new AppExit option Suicide for use on pre-Vista
132 systems. When AppExit is Suicide don't stop the service but exit
133 inelegantly, which should be seen as a failure.
137 * Send properly formatted messages to the event log.
139 * Fixed truncation of very long path lengths in the registry.
143 * Decide how to handle application exit.
145 When the service exits with exit code n look in
146 HKLM\SYSTEM\CurrentControlSet\Services\<service>\Parameters\AppExit\<n>,
147 falling back to the unnamed value if no such code is listed. Parse the
148 (string) value of this entry as follows:
150 Restart: Start the application again (NSSM default).
151 Ignore: Do nothing (srvany default).
152 Exit: Stop the service.
156 * Added support for building a 64-bit executable.
158 * Added project files for newer versions of Visual Studio.