3 * NSSM once again calls TerminateProcess() correctly.
\r
7 * NSSM no longer clutters the event log with "The specified
\r
8 procedure could not be found" on legacy Windows releases.
\r
10 * Fixed failure to set a local username to run the service.
\r
14 * Existing services can now be managed using the GUI
\r
15 or on the command line.
\r
17 * NSSM can now set the priority class and processor
\r
18 affinity of the managed application.
\r
20 * NSSM can now apply an unconditional delay before
\r
21 restarting the application.
\r
23 * NSSM can now optionally rotate existing files when
\r
26 * Unqualified path names are now relative to the
\r
27 application startup directory when redirecting I/O.
\r
29 * NSSM can now set the service display name, description,
\r
30 startup type and log on details.
\r
32 * All services now receive a standard console window,
\r
33 allowing them to read input correctly (if running in
\r
38 * Services installed from the GUI no longer have incorrect
\r
39 AppParameters set in the registry.
\r
43 * Services installed from the commandline without using the
\r
44 GUI no longer have incorrect AppStopMethod* registry
\r
49 * Support AppEnvironmentExtra to append to the environment
\r
50 instead of replacing it.
\r
52 * The GUI is significantly less sucky.
\r
56 * Timeouts for each shutdown method can be configured in
\r
59 * The GUI is slightly less sucky.
\r
63 * NSSM can now redirect the service's I/O streams to any path
\r
64 capable of being opened by CreateFile().
\r
66 * Allow building on Visual Studio Express.
\r
68 * Silently ignore INTERROGATE control.
\r
70 * Try to send Control-C events to console applications when
\r
75 * Fixed case where NSSM could kill unrelated processes when
\r
80 * NSSM is now translated into Italian.
\r
82 * Fixed GUI not allowing paths longer than 256 characters.
\r
86 * Fixed default GUI language being French not English.
\r
90 * Fixed failure to run on Windows 2000.
\r
94 * NSSM is now translated into French.
\r
96 * Really ensure systems recovery actions can happen.
\r
98 The change supposedly introduced in v2.4 to allow service recovery
\r
99 actions to be activated when the application exits gracefully with
\r
100 a non-zero error code didn't actually work.
\r
104 * Support AppEnvironment for compatibility with srvany.
\r
108 * Fixed failure to compile messages.mc in paths containing spaces.
\r
110 * Fixed edge case with CreateProcess().
\r
112 Correctly handle the case where the application executable is under
\r
113 a path which contains space and an executable sharing the initial
\r
114 part of that path (up to a space) exists.
\r
118 * Fixed failure to run on Windows versions prior to Vista.
\r
122 * Read Application, AppDirectory and AppParameters before each restart so
\r
123 a change to any one doesn't require restarting NSSM itself.
\r
125 * Fixed messages not being sent to the event log correctly in some
\r
128 * Try to handle (strictly incorrect) quotes in AppDirectory.
\r
130 Windows directories aren't allowed to contain quotes so CreateProcess()
\r
131 will fail if the AppDirectory is quoted. Note that it succeeds even if
\r
132 Application itself is quoted as the application plus parameters are
\r
133 interpreted as a command line.
\r
135 * Fixed failed to write full arguments to AppParameters when
\r
136 installing a service.
\r
138 * Throttle restarts.
\r
140 Back off from restarting the application immediately if it starts
\r
141 successfully but exits too soon. The default value of "too soon" is
\r
142 1500 milliseconds. This can be configured by adding a DWORD value
\r
143 AppThrottle to the registry.
\r
145 Handle resume messages from the service console to restart the
\r
146 application immediately even if it is throttled.
\r
148 * Try to kill the process tree gracefully.
\r
150 Before calling TerminateProcess() on all processes assocatiated with
\r
151 the monitored application, enumerate all windows and threads and
\r
152 post appropriate messages to them. If the application bothers to
\r
153 listen for such messages it has a chance to shut itself down gracefully.
\r
157 * Handle missing registry values.
\r
159 Warn if AppParameters is missing. Warn if AppDirectory is missing or
\r
160 unset and choose a fallback directory.
\r
161 First try to find the parent directory of the application. If that
\r
162 fails, eg because the application path is just "notepad" or something,
\r
163 start in the Windows directory.
\r
165 * Kill process tree when stopping service.
\r
167 Ensure that all child processes of the monitored application are
\r
168 killed when the service stops by recursing through all running
\r
169 processes and terminating those whose parent is the application
\r
170 or one of its descendents.
\r
174 * Removed incorrect ExpandEnvironmentStrings() error.
\r
176 A log_event() call was inadvertently left in the code causing an error
\r
177 to be set to the eventlog saying that ExpandEnvironmentStrings() had
\r
178 failed when it had actually succeeded.
\r
182 * Allow use of REG_EXPAND_SZ values in the registry.
\r
184 * Don't suicide on exit status 0 by default.
\r
186 Suiciding when the application exits 0 will cause recovery actions to be
\r
187 taken. Usually this is inappropriate. Only suicide if there is an
\r
188 explicit AppExit value for 0 in the registry.
\r
190 Technically such behaviour could be abused to do something like run a
\r
191 script after successful completion of a service but in most cases a
\r
192 suicide is undesirable when no actual failure occurred.
\r
194 * Don't hang if startup parameters couldn't be determined.
\r
195 Instead, signal that the service entered the STOPPED state.
\r
196 Set START_PENDING state prior to actual startup.
\r
200 * Ensure systems recovery actions can happen.
\r
202 In Windows versions earlier than Vista the service manager would only
\r
203 consider a service failed (and hence eligible for recovery action) if
\r
204 the service exited without setting its state to SERVICE_STOPPED, even if
\r
205 it signalled an error exit code.
\r
206 In Vista and later the service manager can be configured to treat a
\r
207 graceful shutdown with error code as a failure but this is not the
\r
210 Try to configure the service manager to use the new behaviour when
\r
211 starting the service so users who set AppExit to Exit can use recovery
\r
212 actions as expected.
\r
214 Also recognise the new AppExit option Suicide for use on pre-Vista
\r
215 systems. When AppExit is Suicide don't stop the service but exit
\r
216 inelegantly, which should be seen as a failure.
\r
220 * Send properly formatted messages to the event log.
\r
222 * Fixed truncation of very long path lengths in the registry.
\r
226 * Decide how to handle application exit.
\r
228 When the service exits with exit code n look in
\r
229 HKLM\SYSTEM\CurrentControlSet\Services\<service>\Parameters\AppExit\<n>,
\r
230 falling back to the unnamed value if no such code is listed. Parse the
\r
231 (string) value of this entry as follows:
\r
233 Restart: Start the application again (NSSM default).
\r
234 Ignore: Do nothing (srvany default).
\r
235 Exit: Stop the service.
\r
239 * Added support for building a 64-bit executable.
\r
241 * Added project files for newer versions of Visual Studio.
\r