LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

posix_spawn.3: Clarify by using name of steps rather than syscalls 

The implementation of the fork() step in posix_spawn(2) relies on
either fork(2), vfork(2) or clone(2) depending on the version of
the glibc and the arguments passed to posix_spawn(2).

It is sometimes ambiguous whether, when we are mentioning
"fork(2)", we are referring to the fork() step or the actual
fork(2) syscall.

This patch hopefully avoids the ambiguity by replacing confusing
occurrences by "the xxx() step" where appropriate.

Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Signed-off-by: Olivier Gayot <olivier.gayot@sigexec.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Olivier Gayot 2018-10-16 21:37:50 +02:00 committed by Michael Kerrisk
parent 8b5b47e983
commit 0b78e0f5f2
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
man3/posix_spawn.3
View File

@ -220,10 +220,10 @@ the requested file.
.PP
.SS pre-exec() step: housekeeping
In between the
.BR fork (2)
.BR fork()
and the
.BR exec (3),
a child process may need to perform a set of housekeeping actions.
.BR exec()
steps, a child process may need to perform a set of housekeeping actions.
The
.BR posix_spawn ()
and
@ -478,8 +478,8 @@ and
place the PID of the child process in
.IR pid ,
and return 0.
If there is an error before or during the
.BR fork (2),
If there is an error during the
.BR fork() step,
then no child is created,
the contents of
.IR *pid