From 6f774da50e657703d3fd9b6fd1f690d25bd7cb3d Mon Sep 17 00:00:00 2001 From: mtkennerly Date: Sat, 18 Nov 2023 00:28:30 +0800 Subject: [PATCH] #39: Add --name to example using sc --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index e085393..ce6f93b 100644 --- a/README.md +++ b/README.md @@ -11,7 +11,7 @@ options from the command that you'd like it to run): * Using Shawl's `add` command: * `shawl add --name my-app -- C:/path/my-app.exe` * Using the Windows `sc` command for more control: - * `sc create my-app binPath= "C:/path/shawl.exe run -- C:/path/my-app.exe"` + * `sc create my-app binPath= "C:/path/shawl.exe run --name my-app -- C:/path/my-app.exe"` * Then start or configure the service as normal: * ``` sc config my-app start= auto @@ -32,8 +32,8 @@ status to Windows: the exit code to Windows as a service-specific error, unless the exit code is 0 or a code you've configured with `--pass`. -Shawl creates a log file for each service, `shawl_for__*.log`, in the -same location as the Shawl executable, with both its own messages and the output +Shawl creates a log file for each service, `shawl_for__*.log` (based on the `--name`), +in the same location as the Shawl executable, with both its own messages and the output from the commands that it runs. If anything goes wrong, you can read the log to find out more. You can disable all logging with `--no-log`, and you can disable just the command logs with `--no-log-cmd`. Each log file is limited to 2 MB, and