3 * NSSM can now optionally rotate existing files when
6 * Unqualified path names are now relative to the
7 application startup directory when redirecting I/O.
9 * NSSM can now set the service display name, description,
10 startup type and log on details.
14 * Services installed from the GUI no longer have incorrect
15 AppParameters set in the registry.
19 * Services installed from the commandline without using the
20 GUI no longer have incorrect AppStopMethod* registry
25 * Support AppEnvironmentExtra to append to the environment
26 instead of replacing it.
28 * The GUI is significantly less sucky.
32 * Timeouts for each shutdown method can be configured in
35 * The GUI is slightly less sucky.
39 * NSSM can now redirect the service's I/O streams to any path
40 capable of being opened by CreateFile().
42 * Allow building on Visual Studio Express.
44 * Silently ignore INTERROGATE control.
46 * Try to send Control-C events to console applications when
51 * Fixed case where NSSM could kill unrelated processes when
56 * NSSM is now translated into Italian.
58 * Fixed GUI not allowing paths longer than 256 characters.
62 * Fixed default GUI language being French not English.
66 * Fixed failure to run on Windows 2000.
70 * NSSM is now translated into French.
72 * Really ensure systems recovery actions can happen.
74 The change supposedly introduced in v2.4 to allow service recovery
75 actions to be activated when the application exits gracefully with
76 a non-zero error code didn't actually work.
80 * Support AppEnvironment for compatibility with srvany.
84 * Fixed failure to compile messages.mc in paths containing spaces.
86 * Fixed edge case with CreateProcess().
88 Correctly handle the case where the application executable is under
89 a path which contains space and an executable sharing the initial
90 part of that path (up to a space) exists.
94 * Fixed failure to run on Windows versions prior to Vista.
98 * Read Application, AppDirectory and AppParameters before each restart so
99 a change to any one doesn't require restarting NSSM itself.
101 * Fixed messages not being sent to the event log correctly in some
104 * Try to handle (strictly incorrect) quotes in AppDirectory.
106 Windows directories aren't allowed to contain quotes so CreateProcess()
107 will fail if the AppDirectory is quoted. Note that it succeeds even if
108 Application itself is quoted as the application plus parameters are
109 interpreted as a command line.
111 * Fixed failed to write full arguments to AppParameters when
112 installing a service.
116 Back off from restarting the application immediately if it starts
117 successfully but exits too soon. The default value of "too soon" is
118 1500 milliseconds. This can be configured by adding a DWORD value
119 AppThrottle to the registry.
121 Handle resume messages from the service console to restart the
122 application immediately even if it is throttled.
124 * Try to kill the process tree gracefully.
126 Before calling TerminateProcess() on all processes assocatiated with
127 the monitored application, enumerate all windows and threads and
128 post appropriate messages to them. If the application bothers to
129 listen for such messages it has a chance to shut itself down gracefully.
133 * Handle missing registry values.
135 Warn if AppParameters is missing. Warn if AppDirectory is missing or
136 unset and choose a fallback directory.
137 First try to find the parent directory of the application. If that
138 fails, eg because the application path is just "notepad" or something,
139 start in the Windows directory.
141 * Kill process tree when stopping service.
143 Ensure that all child processes of the monitored application are
144 killed when the service stops by recursing through all running
145 processes and terminating those whose parent is the application
146 or one of its descendents.
150 * Removed incorrect ExpandEnvironmentStrings() error.
152 A log_event() call was inadvertently left in the code causing an error
153 to be set to the eventlog saying that ExpandEnvironmentStrings() had
154 failed when it had actually succeeded.
158 * Allow use of REG_EXPAND_SZ values in the registry.
160 * Don't suicide on exit status 0 by default.
162 Suiciding when the application exits 0 will cause recovery actions to be
163 taken. Usually this is inappropriate. Only suicide if there is an
164 explicit AppExit value for 0 in the registry.
166 Technically such behaviour could be abused to do something like run a
167 script after successful completion of a service but in most cases a
168 suicide is undesirable when no actual failure occurred.
170 * Don't hang if startup parameters couldn't be determined.
171 Instead, signal that the service entered the STOPPED state.
172 Set START_PENDING state prior to actual startup.
176 * Ensure systems recovery actions can happen.
178 In Windows versions earlier than Vista the service manager would only
179 consider a service failed (and hence eligible for recovery action) if
180 the service exited without setting its state to SERVICE_STOPPED, even if
181 it signalled an error exit code.
182 In Vista and later the service manager can be configured to treat a
183 graceful shutdown with error code as a failure but this is not the
186 Try to configure the service manager to use the new behaviour when
187 starting the service so users who set AppExit to Exit can use recovery
190 Also recognise the new AppExit option Suicide for use on pre-Vista
191 systems. When AppExit is Suicide don't stop the service but exit
192 inelegantly, which should be seen as a failure.
196 * Send properly formatted messages to the event log.
198 * Fixed truncation of very long path lengths in the registry.
202 * Decide how to handle application exit.
204 When the service exits with exit code n look in
205 HKLM\SYSTEM\CurrentControlSet\Services\<service>\Parameters\AppExit\<n>,
206 falling back to the unnamed value if no such code is listed. Parse the
207 (string) value of this entry as follows:
209 Restart: Start the application again (NSSM default).
210 Ignore: Do nothing (srvany default).
211 Exit: Stop the service.
215 * Added support for building a 64-bit executable.
217 * Added project files for newer versions of Visual Studio.