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