simulating a Control-C keypress. If they have installed a handler routine\r
they can clean up and shut down gracefully on receipt of the event.\r
\r
+Since version 2.17, NSSM can redirect the managed application's I/O streams\r
+to an arbitrary path.\r
+\r
+\r
Usage\r
-----\r
In the usage notes below, arguments to the program may be written in angle \r
If only the default action is set to Suicide NSSM will instead exit gracefully.\r
\r
\r
+I/O redirection\r
+---------------\r
+NSSM can redirect the managed application's I/O to any path capable of being\r
+opened by CreateFile(). This enables, for example, capturing the log output\r
+of an application which would otherwise only write to the console or accepting\r
+input from a serial port.\r
+\r
+NSSM will look in the registry under\r
+HKLM\SYSTEM\CurrentControlSet\Services\<service>\Parameters for the keys\r
+corresponding to arguments to CreateFile(). All are optional. If no path is\r
+given for a particular stream it will not be redirected. If a path is given\r
+but any of the other values are omitted they will be receive sensible defaults.\r
+\r
+ AppStdin: Path to receive input.\r
+ AppStdout: Path to receive output.\r
+ AppStderr: Path to receive error output.\r
+\r
+Parameters for CreateFile() are providing with the "AppStdinShareMode",\r
+"AppStdinCreationDisposition" and "AppStdinFlagsAndAttributes" values (and\r
+analogously for stdout and stderr).\r
+\r
+In general, if you want the service to log its output, set AppStdout and\r
+AppStderr to the same path, eg C:\Users\Public\service.log, and it should\r
+work. Remember, however, that the path must be accessible to the user\r
+running the service.\r
+\r
+\r
Removing services using the GUI\r
-------------------------------\r
NSSM can also remove services. Run\r