From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/1] fork.2: child and parent run in separate memory spaces
Date: Tue, 17 Feb 2015 06:05:44 +0100 [thread overview]
Message-ID: <54E2CC28.4070008@gmail.com> (raw)
In-Reply-To: <1424083246-6162-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
On 02/16/2015 11:40 AM, Heinrich Schuchardt wrote:
> fork.2 should clearly point out that child and parent
> process run in separate memory spaces.
Thanks, Heinrich. Applied.
Cheers,
Michael
> Signed-off-by: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
> ---
> man2/fork.2 | 22 +++++++++++++++++++---
> 1 file changed, 19 insertions(+), 3 deletions(-)
>
> diff --git a/man2/fork.2 b/man2/fork.2
> index e6695ad..dce9bff 100644
> --- a/man2/fork.2
> +++ b/man2/fork.2
> @@ -46,9 +46,25 @@ fork \- create a child process
> .SH DESCRIPTION
> .BR fork ()
> creates a new process by duplicating the calling process.
> -The new process, referred to as the \fIchild\fP,
> -is an exact duplicate of the calling process,
> -referred to as the \fIparent\fP, except for the following points:
> +The new process is referred to as the
> +.I child
> +process.
> +The calling process is referred to as the
> +.I parent
> +process.
> +
> +The child process and the parent process run in separate memory spaces.
> +At the time of
> +.BR fork ()
> +both memory spaces have the same content.
> +Memory writes, file mappings
> +.RB ( mmap (2)),
> +and unmappings
> +.RB ( munmap (2))
> +performed by one of the processes do not affect the other.
> +
> +The child process is an exact duplicate of the parent
> +process except for the following points:
> .IP * 3
> The child has its own unique process ID,
> and this PID does not match the ID of any existing process group
>
--
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
prev parent reply other threads:[~2015-02-17 5:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 10:40 [PATCH 1/1] fork.2: child and parent run in separate memory spaces Heinrich Schuchardt
[not found] ` <1424083246-6162-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
2015-02-17 5:05 ` Michael Kerrisk (man-pages) [this message]
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=54E2CC28.4070008@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=xypron.glpk-Mmb7MZpHnFY@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.