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