Skip to content

Commit 62298e0

Browse files
committed
posix_spawn() does not have to be implemented as a syscall
1 parent 010eaf3 commit 62298e0

File tree

1 file changed

+4
-6
lines changed

1 file changed

+4
-6
lines changed

proc.tex

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -909,12 +909,10 @@
909909
\item Note that you have to use macros from the previous slide to get the
910910
child's return value out of the status information.
911911
\item \label{WAITPID} Example: \example{wait/wait.c}
912-
\item \label{SPAWN} Creating new process with \texttt{fork} and replacing the
913-
process address space etc. with a new one after \texttt{exec} has been done is
914-
expensive and has other problems. To make kernel create new process directly
915-
from executable \texttt{posix\_spawn} can be used. The new process can be waited
916-
on with \texttt{waitpid} etc. just like in the case of \texttt{fork}.
917-
Example: \example{exec/spawn.c}
912+
\item \label{SPAWN} Alternative for the \texttt{fork}/\texttt{exec} combination
913+
can be the \texttt{posix\_spawn} function. The new process using this function
914+
can be waited on with \texttt{waitpid} etc. just like in the case of
915+
\texttt{fork}. Example: \example{exec/spawn.c}
918916
\end{itemize}
919917

920918
%%%%%

0 commit comments

Comments
 (0)