lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Poirier <benjamin.poirier@gmail.com>
To: lttng-dev@lists.lttng.org
Subject: [PATCH] doc: Fix bind address example for lttng-relayd
Date: Mon,  6 Jan 2020 14:19:54 +0900	[thread overview]
Message-ID: <20200106051954.138370-1-benjamin.poirier__47900.9766875365$1578288039$gmane$org@gmail.com> (raw)

INADDR_ANY is 0.0.0.0

Fixes: c93eadade277 ("doc/man: use propagated default values in man pages")
Signed-off-by: Benjamin Poirier <benjamin.poirier@gmail.com>
---
 doc/man/lttng-relayd.8.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/man/lttng-relayd.8.txt b/doc/man/lttng-relayd.8.txt
index be59675d..bf88a535 100644
--- a/doc/man/lttng-relayd.8.txt
+++ b/doc/man/lttng-relayd.8.txt
@@ -40,7 +40,7 @@ it can write to the output directory and listen on the configured ports.
 If a user is within a secured network and/or has proper firewall
 settings, `lttng-relayd` can listen to LTTng live connections from _all_
 network interfaces by specifying
-+--live-port=tcp://{default_network_viewer_bind_address}:{default_network_viewer_port}+.
++--live-port=tcp://0.0.0.0:{default_network_viewer_port}+.
 
 Once a trace has been streamed completely, the trace can be processed by
 any tool that can process an LTTng trace located on the local
-- 
2.25.0.rc0

             reply	other threads:[~2020-01-06  5:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-06  5:19 Benjamin Poirier [this message]
     [not found] <20200106051954.138370-1-benjamin.poirier@gmail.com>
2020-01-06 14:39 ` [PATCH] doc: Fix bind address example for lttng-relayd Mathieu Desnoyers
     [not found] ` <2006658589.17563.1578321593973.JavaMail.zimbra@efficios.com>
2020-01-07  1:58   ` Benjamin Poirier
     [not found]   ` <20200107015843.GA159599@f3>
2020-01-07 16:14     ` Mathieu Desnoyers
2020-01-15  0:45 ` Jérémie Galarneau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='20200106051954.138370-1-benjamin.poirier__47900.9766875365$1578288039$gmane$org@gmail.com' \
    --to=benjamin.poirier@gmail.com \
    --cc=lttng-dev@lists.lttng.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).