3 * Services installed from the GUI no longer have incorrect
4 AppParameters set in the registry.
8 * Services installed from the commandline without using the
9 GUI no longer have incorrect AppStopMethod* registry
14 * Support AppEnvironmentExtra to append to the environment
15 instead of replacing it.
17 * The GUI is significantly less sucky.
21 * Timeouts for each shutdown method can be configured in
24 * The GUI is slightly less sucky.
28 * NSSM can now redirect the service's I/O streams to any path
29 capable of being opened by CreateFile().
31 * Allow building on Visual Studio Express.
33 * Silently ignore INTERROGATE control.
35 * Try to send Control-C events to console applications when
40 * Fixed case where NSSM could kill unrelated processes when
45 * NSSM is now translated into Italian.
47 * Fixed GUI not allowing paths longer than 256 characters.
51 * Fixed default GUI language being French not English.
55 * Fixed failure to run on Windows 2000.
59 * NSSM is now translated into French.
61 * Really ensure systems recovery actions can happen.
63 The change supposedly introduced in v2.4 to allow service recovery
64 actions to be activated when the application exits gracefully with
65 a non-zero error code didn't actually work.
69 * Support AppEnvironment for compatibility with srvany.
73 * Fixed failure to compile messages.mc in paths containing spaces.
75 * Fixed edge case with CreateProcess().
77 Correctly handle the case where the application executable is under
78 a path which contains space and an executable sharing the initial
79 part of that path (up to a space) exists.
83 * Fixed failure to run on Windows versions prior to Vista.
87 * Read Application, AppDirectory and AppParameters before each restart so
88 a change to any one doesn't require restarting NSSM itself.
90 * Fixed messages not being sent to the event log correctly in some
93 * Try to handle (strictly incorrect) quotes in AppDirectory.
95 Windows directories aren't allowed to contain quotes so CreateProcess()
96 will fail if the AppDirectory is quoted. Note that it succeeds even if
97 Application itself is quoted as the application plus parameters are
98 interpreted as a command line.
100 * Fixed failed to write full arguments to AppParameters when
101 installing a service.
105 Back off from restarting the application immediately if it starts
106 successfully but exits too soon. The default value of "too soon" is
107 1500 milliseconds. This can be configured by adding a DWORD value
108 AppThrottle to the registry.
110 Handle resume messages from the service console to restart the
111 application immediately even if it is throttled.
113 * Try to kill the process tree gracefully.
115 Before calling TerminateProcess() on all processes assocatiated with
116 the monitored application, enumerate all windows and threads and
117 post appropriate messages to them. If the application bothers to
118 listen for such messages it has a chance to shut itself down gracefully.
122 * Handle missing registry values.
124 Warn if AppParameters is missing. Warn if AppDirectory is missing or
125 unset and choose a fallback directory.
126 First try to find the parent directory of the application. If that
127 fails, eg because the application path is just "notepad" or something,
128 start in the Windows directory.
130 * Kill process tree when stopping service.
132 Ensure that all child processes of the monitored application are
133 killed when the service stops by recursing through all running
134 processes and terminating those whose parent is the application
135 or one of its descendents.
139 * Removed incorrect ExpandEnvironmentStrings() error.
141 A log_event() call was inadvertently left in the code causing an error
142 to be set to the eventlog saying that ExpandEnvironmentStrings() had
143 failed when it had actually succeeded.
147 * Allow use of REG_EXPAND_SZ values in the registry.
149 * Don't suicide on exit status 0 by default.
151 Suiciding when the application exits 0 will cause recovery actions to be
152 taken. Usually this is inappropriate. Only suicide if there is an
153 explicit AppExit value for 0 in the registry.
155 Technically such behaviour could be abused to do something like run a
156 script after successful completion of a service but in most cases a
157 suicide is undesirable when no actual failure occurred.
159 * Don't hang if startup parameters couldn't be determined.
160 Instead, signal that the service entered the STOPPED state.
161 Set START_PENDING state prior to actual startup.
165 * Ensure systems recovery actions can happen.
167 In Windows versions earlier than Vista the service manager would only
168 consider a service failed (and hence eligible for recovery action) if
169 the service exited without setting its state to SERVICE_STOPPED, even if
170 it signalled an error exit code.
171 In Vista and later the service manager can be configured to treat a
172 graceful shutdown with error code as a failure but this is not the
175 Try to configure the service manager to use the new behaviour when
176 starting the service so users who set AppExit to Exit can use recovery
179 Also recognise the new AppExit option Suicide for use on pre-Vista
180 systems. When AppExit is Suicide don't stop the service but exit
181 inelegantly, which should be seen as a failure.
185 * Send properly formatted messages to the event log.
187 * Fixed truncation of very long path lengths in the registry.
191 * Decide how to handle application exit.
193 When the service exits with exit code n look in
194 HKLM\SYSTEM\CurrentControlSet\Services\<service>\Parameters\AppExit\<n>,
195 falling back to the unnamed value if no such code is listed. Parse the
196 (string) value of this entry as follows:
198 Restart: Start the application again (NSSM default).
199 Ignore: Do nothing (srvany default).
200 Exit: Stop the service.
204 * Added support for building a 64-bit executable.
206 * Added project files for newer versions of Visual Studio.