3 * Support AppEnvironmentExtra to append to the environment
4 instead of replacing it.
6 * The GUI is significantly less sucky.
10 * Timeouts for each shutdown method can be configured in
13 * The GUI is slightly less sucky.
17 * NSSM can now redirect the service's I/O streams to any path
18 capable of being opened by CreateFile().
20 * Allow building on Visual Studio Express.
22 * Silently ignore INTERROGATE control.
24 * Try to send Control-C events to console applications when
29 * Fixed case where NSSM could kill unrelated processes when
34 * NSSM is now translated into Italian.
36 * Fixed GUI not allowing paths longer than 256 characters.
40 * Fixed default GUI language being French not English.
44 * Fixed failure to run on Windows 2000.
48 * NSSM is now translated into French.
50 * Really ensure systems recovery actions can happen.
52 The change supposedly introduced in v2.4 to allow service recovery
53 actions to be activated when the application exits gracefully with
54 a non-zero error code didn't actually work.
58 * Support AppEnvironment for compatibility with srvany.
62 * Fixed failure to compile messages.mc in paths containing spaces.
64 * Fixed edge case with CreateProcess().
66 Correctly handle the case where the application executable is under
67 a path which contains space and an executable sharing the initial
68 part of that path (up to a space) exists.
72 * Fixed failure to run on Windows versions prior to Vista.
76 * Read Application, AppDirectory and AppParameters before each restart so
77 a change to any one doesn't require restarting NSSM itself.
79 * Fixed messages not being sent to the event log correctly in some
82 * Try to handle (strictly incorrect) quotes in AppDirectory.
84 Windows directories aren't allowed to contain quotes so CreateProcess()
85 will fail if the AppDirectory is quoted. Note that it succeeds even if
86 Application itself is quoted as the application plus parameters are
87 interpreted as a command line.
89 * Fixed failed to write full arguments to AppParameters when
94 Back off from restarting the application immediately if it starts
95 successfully but exits too soon. The default value of "too soon" is
96 1500 milliseconds. This can be configured by adding a DWORD value
97 AppThrottle to the registry.
99 Handle resume messages from the service console to restart the
100 application immediately even if it is throttled.
102 * Try to kill the process tree gracefully.
104 Before calling TerminateProcess() on all processes assocatiated with
105 the monitored application, enumerate all windows and threads and
106 post appropriate messages to them. If the application bothers to
107 listen for such messages it has a chance to shut itself down gracefully.
111 * Handle missing registry values.
113 Warn if AppParameters is missing. Warn if AppDirectory is missing or
114 unset and choose a fallback directory.
115 First try to find the parent directory of the application. If that
116 fails, eg because the application path is just "notepad" or something,
117 start in the Windows directory.
119 * Kill process tree when stopping service.
121 Ensure that all child processes of the monitored application are
122 killed when the service stops by recursing through all running
123 processes and terminating those whose parent is the application
124 or one of its descendents.
128 * Removed incorrect ExpandEnvironmentStrings() error.
130 A log_event() call was inadvertently left in the code causing an error
131 to be set to the eventlog saying that ExpandEnvironmentStrings() had
132 failed when it had actually succeeded.
136 * Allow use of REG_EXPAND_SZ values in the registry.
138 * Don't suicide on exit status 0 by default.
140 Suiciding when the application exits 0 will cause recovery actions to be
141 taken. Usually this is inappropriate. Only suicide if there is an
142 explicit AppExit value for 0 in the registry.
144 Technically such behaviour could be abused to do something like run a
145 script after successful completion of a service but in most cases a
146 suicide is undesirable when no actual failure occurred.
148 * Don't hang if startup parameters couldn't be determined.
149 Instead, signal that the service entered the STOPPED state.
150 Set START_PENDING state prior to actual startup.
154 * Ensure systems recovery actions can happen.
156 In Windows versions earlier than Vista the service manager would only
157 consider a service failed (and hence eligible for recovery action) if
158 the service exited without setting its state to SERVICE_STOPPED, even if
159 it signalled an error exit code.
160 In Vista and later the service manager can be configured to treat a
161 graceful shutdown with error code as a failure but this is not the
164 Try to configure the service manager to use the new behaviour when
165 starting the service so users who set AppExit to Exit can use recovery
168 Also recognise the new AppExit option Suicide for use on pre-Vista
169 systems. When AppExit is Suicide don't stop the service but exit
170 inelegantly, which should be seen as a failure.
174 * Send properly formatted messages to the event log.
176 * Fixed truncation of very long path lengths in the registry.
180 * Decide how to handle application exit.
182 When the service exits with exit code n look in
183 HKLM\SYSTEM\CurrentControlSet\Services\<service>\Parameters\AppExit\<n>,
184 falling back to the unnamed value if no such code is listed. Parse the
185 (string) value of this entry as follows:
187 Restart: Start the application again (NSSM default).
188 Ignore: Do nothing (srvany default).
189 Exit: Stop the service.
193 * Added support for building a 64-bit executable.
195 * Added project files for newer versions of Visual Studio.