Skip to content

Commit a580259

Browse files
committed
fix doc typos
1 parent 724fdf9 commit a580259

File tree

4 files changed

+7
-7
lines changed

4 files changed

+7
-7
lines changed

userspace/sysdig/man/csysdig.8

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -421,14 +421,14 @@ argument (e.g.
421421
<http://admin:password@127.0.0.1:5050>).
422422
Mesos url is required.
423423
Marathon url is optional, defaulting to auto\-follow \- if Marathon API
424-
server is not provided, sysdig will attempt to retrieve (and
424+
server is not provided, csysdig will attempt to retrieve (and
425425
subsequently follow, if it migrates) the location of Marathon API server
426426
from the Mesos master.
427-
Note that, with auto\-follow, sysdig will likely receive a cluster
428-
internal IP address for Marathon API server, so running sysdig with
427+
Note that, with auto\-follow, csysdig will likely receive a cluster
428+
internal IP address for Marathon API server, so running csysdig with
429429
Marathon auto\-follow from a node that is not part of Mesos cluster may
430430
not work.
431-
Additionally, running sydig with Mesos support on a node that has no
431+
Additionally, running csysdig with Mesos support on a node that has no
432432
containers managed by Mesos is of limited use because, although cluster
433433
metadata will be collected, there will be no Mesos/Marathon filtering
434434
capability.

userspace/sysdig/man/csysdig.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -182,7 +182,7 @@ COMMAND LINE OPTIONS
182182
Print program logs into the given file.
183183

184184
**-m** _url[,marathon-url]_, **--mesos-api=**_url[,marathon-url]_
185-
Enable Mesos support by connecting to the API server specified as argument (e.g. http://admin:password@127.0.0.1:5050). Mesos url is required. Marathon url is optional, defaulting to auto-follow - if Marathon API server is not provided, sysdig will attempt to retrieve (and subsequently follow, if it migrates) the location of Marathon API server from the Mesos master. Note that, with auto-follow, sysdig will likely receive a cluster internal IP address for Marathon API server, so running sysdig with Marathon auto-follow from a node that is not part of Mesos cluster may not work. Additionally, running sydig with Mesos support on a node that has no containers managed by Mesos is of limited use because, although cluster metadata will be collected, there will be no Mesos/Marathon filtering capability. The API servers can also be specified via the environment variable SYSDIG_MESOS_API.
185+
Enable Mesos support by connecting to the API server specified as argument (e.g. http://admin:password@127.0.0.1:5050). Mesos url is required. Marathon url is optional, defaulting to auto-follow - if Marathon API server is not provided, csysdig will attempt to retrieve (and subsequently follow, if it migrates) the location of Marathon API server from the Mesos master. Note that, with auto-follow, csysdig will likely receive a cluster internal IP address for Marathon API server, so running csysdig with Marathon auto-follow from a node that is not part of Mesos cluster may not work. Additionally, running csysdig with Mesos support on a node that has no containers managed by Mesos is of limited use because, although cluster metadata will be collected, there will be no Mesos/Marathon filtering capability. The API servers can also be specified via the environment variable SYSDIG_MESOS_API.
186186

187187
**-N**
188188
Don't convert port numbers to names.

userspace/sysdig/man/sysdig.8

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -406,7 +406,7 @@ Note that, with auto\-follow, sysdig will likely receive a cluster
406406
internal IP address for Marathon API server, so running sysdig with
407407
Marathon auto\-follow from a node that is not part of Mesos cluster may
408408
not work.
409-
Additionally, running sydig with Mesos support on a node that has no
409+
Additionally, running sysdig with Mesos support on a node that has no
410410
containers managed by Mesos is of limited use because, although cluster
411411
metadata will be collected, there will be no Mesos/Marathon filtering
412412
capability.

userspace/sysdig/man/sysdig.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -154,7 +154,7 @@ OPTIONS
154154
List the fields that can be used for filtering and output formatting. Use -lv to get additional information for each field.
155155

156156
**-m** _url[,marathon-url]_, **--mesos-api=**_url[,marathon-url]_
157-
Enable Mesos support by connecting to the API server specified as argument (e.g. http://admin:password@127.0.0.1:5050). Mesos url is required. Marathon url is optional, defaulting to auto-follow - if Marathon API server is not provided, sysdig will attempt to retrieve (and subsequently follow, if it migrates) the location of Marathon API server from the Mesos master. Note that, with auto-follow, sysdig will likely receive a cluster internal IP address for Marathon API server, so running sysdig with Marathon auto-follow from a node that is not part of Mesos cluster may not work. Additionally, running sydig with Mesos support on a node that has no containers managed by Mesos is of limited use because, although cluster metadata will be collected, there will be no Mesos/Marathon filtering capability. The API servers can also be specified via the environment variable SYSDIG_MESOS_API.
157+
Enable Mesos support by connecting to the API server specified as argument (e.g. http://admin:password@127.0.0.1:5050). Mesos url is required. Marathon url is optional, defaulting to auto-follow - if Marathon API server is not provided, sysdig will attempt to retrieve (and subsequently follow, if it migrates) the location of Marathon API server from the Mesos master. Note that, with auto-follow, sysdig will likely receive a cluster internal IP address for Marathon API server, so running sysdig with Marathon auto-follow from a node that is not part of Mesos cluster may not work. Additionally, running sysdig with Mesos support on a node that has no containers managed by Mesos is of limited use because, although cluster metadata will be collected, there will be no Mesos/Marathon filtering capability. The API servers can also be specified via the environment variable SYSDIG_MESOS_API.
158158

159159
**-N**
160160
Don't convert port numbers to names.

0 commit comments

Comments
 (0)