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