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