Copyright (c) 1980, 1991, 1993 The Regents of the University of California. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the fol...
NAMEvfork - create a new process without copying the address space
SYNOPSISIn unistd.h Ft pid_t Fn vfork void
DESCRIPTIONBf -symbolic Since this function is hard to use correctly from application software, it is recommended to use posix_spawn3 or fork(2) instead. Ef
The Fn vfork system call can be used to create new processes without fully copying the address space of the old process, which is inefficient in a paged environment. It is useful when the purpose of fork(2) would have been to create a new system context for an execve(2). The Fn vfork system call differs from fork(2) in that the child borrows the parent process's address space and the calling thread's stack until a call to execve(2) or an exit (either by a call to _exit2 or abnormally). The calling thread is suspended while the child is using its resources. Other threads continue to run.
The Fn vfork system call returns 0 in the child's context and (later) the pid of the child in the parent's context.
Many problems can occur when replacing fork(2) with Fn vfork . For example, it does not work to return while running in the child's context from the procedure that called Fn vfork since the eventual return from Fn vfork would then return to a no longer existent stack frame. Also, changing process state which is partially implemented in user space such as signal handlers with libthr(3) will corrupt the parent's state.
Be careful, also, to call _exit2 rather than exit(3) if you cannot execve(2), since exit(3) will flush and close standard I/O channels, and thereby mess up the parent processes standard I/O data structures. (Even with fork(2) it is wrong to call exit(3) since buffered data would then be flushed twice.)