linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Kir Kolyshkin <kir-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Cyrill Gorcunov
	<gorcunov-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>,
	criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH 3/4] prctl.2: fix wording in PR_SET_MM_EXE_FILE description
Date: Sat, 22 Feb 2014 10:06:39 +0100	[thread overview]
Message-ID: <5308689F.4050901@gmail.com> (raw)
In-Reply-To: <1392252556-23254-3-git-send-email-kir-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>

Applied!

On 02/13/2014 01:49 AM, Kir Kolyshkin wrote:
> Signed-off-by: Kir Kolyshkin <kir-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
> ---
>  man2/prctl.2 | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/man2/prctl.2 b/man2/prctl.2
> index 55aef52..a2d06d1 100644
> --- a/man2/prctl.2
> +++ b/man2/prctl.2
> @@ -769,8 +769,8 @@ section).
>  The second limitation is that such transitions can be done only once
>  in a process life time.
>  Any further attempts will be rejected.
> -This should help system administrators to monitor unusual
> -symbolic-link transitions over all process running in a system.
> +This should help system administrators monitor unusual
> +symbolic-link transitions over all processes running on a system.
>  .RE
>  .\"
>  .SH RETURN VALUE
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-02-22  9:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13  0:49 [PATCH 1/4] prctl.2: uncomment PR_SET_MM options in Linux 3.5 Kir Kolyshkin
     [not found] ` <1392252556-23254-1-git-send-email-kir-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2014-02-13  0:49   ` [PATCH 2/4] prctl.2: Note PR_SET_MM opts appeared " Kir Kolyshkin
     [not found]     ` <1392252556-23254-2-git-send-email-kir-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2014-02-22  9:06       ` Michael Kerrisk (man-pages)
2014-02-13  0:49   ` [PATCH 3/4] prctl.2: fix wording in PR_SET_MM_EXE_FILE description Kir Kolyshkin
     [not found]     ` <1392252556-23254-3-git-send-email-kir-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2014-02-22  9:06       ` Michael Kerrisk (man-pages) [this message]
2014-02-13  0:49   ` [PATCH 4/4] prctl.2: cite PR_SET_MM kernel commits Kir Kolyshkin
     [not found]     ` <1392252556-23254-4-git-send-email-kir-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2014-02-22  9:06       ` Michael Kerrisk (man-pages)
2014-02-22  9:06   ` [PATCH 1/4] prctl.2: uncomment PR_SET_MM options in Linux 3.5 Michael Kerrisk (man-pages)

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=5308689F.4050901@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
    --cc=gorcunov-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
    --cc=kir-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).