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