lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: Michael Jeanson <mjeanson@efficios.com>
To: lttng-dev@lists.lttng.org
Cc: Jeremie Galarneau <jgalar@efficios.com>
Subject: Re: [PATCH lttng-ust] Docs: LTTNG-UST(3): missing references to some namespace man pages
Date: Thu, 24 Oct 2019 15:12:08 -0400	[thread overview]
Message-ID: <6d1ae176-02b8-203b-3b4c-c8be81ccf4e6__31387.625976798$1571944346$gmane$org@efficios.com> (raw)
In-Reply-To: <20191024190828.147584-1-jeremie.galarneau@efficios.com>

On 2019-10-24 3:08 p.m., Jérémie Galarneau wrote:
> The LTTNG-UST(3) manual page is missing references to the mount,
> network, ipc, and uts namespace man pages.
> 
> Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
> ---
>  doc/man/lttng-ust.3.txt | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/doc/man/lttng-ust.3.txt b/doc/man/lttng-ust.3.txt
> index 1bd4d1e0..2534612a 100644
> --- a/doc/man/lttng-ust.3.txt
> +++ b/doc/man/lttng-ust.3.txt
> @@ -804,15 +804,15 @@ The following man:namespaces(7) context fields are supported by LTTng-UST:
>  
>  `ipc_ns`::
>      System V IPC, POSIX message queues namespace: inode number of the
> -    current IPC namespace in the proc filesystem.
> +    current man:ipc_namespaces(7) namespace in the proc filesystem.
>  
>  `mnt_ns`::
> -    Mount points namespace: inode number of the current Mount namespace
> -    in the proc filesystem.
> +    Mount points namespace: inode number of the current
> +    man:mount_namespaces(7) in the proc filesystem.
>  
>  `net_ns`::
>      Network devices, stacks, ports namespace: inode number of the
> -    current Network namespace in the proc filesystem.
> +    current man:network_namespaces(7) in the proc filesystem.
>  
>  `pid_ns`::
>      Process IDs namespace: inode number of the current
> @@ -824,7 +824,7 @@ The following man:namespaces(7) context fields are supported by LTTng-UST:
>  
>  `uts_ns`::
>      Hostname and NIS domain name namespace: inode number of the
> -    current UTS namespace in the proc filesystem.
> +    current man:uts_namespaces(7) in the proc filesystem.
>  
>  The following man:credentials(7) context fields are supported by LTTng-UST:
>  
> 

The 'ipc_namespaces(7)' and 'uts_namespaces(7)' aren't present on my
system, do you have them on Arch?
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

       reply	other threads:[~2019-10-24 19:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191024190828.147584-1-jeremie.galarneau@efficios.com>
2019-10-24 19:12 ` Michael Jeanson [this message]
     [not found] ` <6d1ae176-02b8-203b-3b4c-c8be81ccf4e6@efficios.com>
2019-10-24 19:17   ` [PATCH lttng-ust] Docs: LTTNG-UST(3): missing references to some namespace man pages Jérémie Galarneau
2019-10-24 19:23 ` Mathieu Desnoyers
2019-10-24 19:08 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='6d1ae176-02b8-203b-3b4c-c8be81ccf4e6__31387.625976798$1571944346$gmane$org@efficios.com' \
    --to=mjeanson@efficios.com \
    --cc=jgalar@efficios.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).