Skip to content

Commit dc0ddcf

Browse files
committed
Fix description about PID_OR_SVCNAME argument
See also: fluent/fluentd#3680 Signed-off-by: Daijiro Fukuda <[email protected]>
1 parent 1e99dc7 commit dc0ddcf

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

deployment/command-line-option.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -161,7 +161,7 @@ Options:
161161
Control `fluentd` process using [Signals](signals.md) or Windows Event.
162162

163163
```text
164-
Usage: fluent-ctl COMMAND PID_OR_SVCNAME
164+
Usage: fluent-ctl COMMAND [PID_OR_SVCNAME]
165165
166166
Commands:
167167
shutdown
@@ -179,10 +179,10 @@ You can specify the process id of the supervisor process.
179179
fluent-ctl shutdown 11111
180180
```
181181

182-
If you run Fluentd as a Windows service, then you have to specify the svcname (the name of the Windows service).
182+
If you run Fluentd as a Windows service, then you can omit `PID_OR_SVCNAME` when the service name is the default value `fluentdwinsvc`.
183183

184184
```text
185-
fluent-ctl dump fluentdwinsvc
185+
fluent-ctl dump
186186
```
187187

188188
### About `dump`
@@ -196,7 +196,7 @@ Since this uses [SIGDUMP](https://github.com/frsyuki/sigdump), you can change th
196196
```Powershell
197197
$ $env:SIGDUMP_PATH="/sigdump/sigdump.log" # The directory `sidgump` has to exist.
198198
$ fuentd -c ...
199-
$ fluent-ctl dump {PID_OR_SVCNAME} # At another shell.
199+
$ fluent-ctl dump # At another shell.
200200
```
201201

202202
Then Fluentd dumps files as following. Each process id is automatically added to the path.

0 commit comments

Comments
 (0)