Hello Olivier, On 10/16/18 9:37 PM, Olivier Gayot wrote: > 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. > > Signed-off-by: Olivier Gayot <olivier.gayot@xxxxxxxxxxx> Thanks. Patch applied. Cheers, Michael > --- > man3/posix_spawn.3 | 10 +++++----- > 1 file changed, 5 insertions(+), 5 deletions(-) > > diff --git a/man3/posix_spawn.3 b/man3/posix_spawn.3 > index 8badb43bf..72e7509d8 100644 > --- a/man3/posix_spawn.3 > +++ b/man3/posix_spawn.3 > @@ -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 > -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
