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