icon Top 9 categories map      RocketAware > man pages >

vfork(2)

Tips: Browse or Search all pages for efficient awareness of more than 6000 of the most popular reusable and open source applications, functions, libraries, and FAQs.


The "RKT couplings" below include links to source code, updates, additional information, advice, FAQs, and overviews.


Home

Search all pages


Subjects

By activity
Professions, Sciences, Humanities, Business, ...

User Interface
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...

Text Strings
Conversions, tests, processing, manipulation,...

Math
Integer, Floating point, Matrix, Statistics, Boolean, ...

Processing
Algorithms, Memory, Process control, Debugging, ...

Stored Data
Data storage, Integrity, Encryption, Compression, ...

Communications
Networks, protocols, Interprocess, Remote, Client Server, ...

Hard World
Timing, Calendar and Clock, Audio, Video, Printer, Controls...

File System
Management, Filtering, File & Directory access, Viewers, ...

    

RocketLink!--> Man page versions: OpenBSD FreeBSD NetBSD Solaris Others



VFORK(2)                  OpenBSD Programmer's Manual                 VFORK(2)

NAME
     vfork - spawn new process and block parent



SYNOPSIS
     #include <unistd.h>

     pid_t
     vfork(void);

DESCRIPTION
     vfork() was originally used to create new processes without fully copying
     the address space of the old process, which is horrendously inefficient
     in a paged environment.  It was useful when the purpose of fork(2) would
     have been to create a new system context for an execve(2).  Since fork(2)
     is now efficient, even in the above case, the need for vfork() has dimin-
     ished.  vfork() differs from fork(2) in that the parent is suspended un-
     til the child makes a call to execve(2) or an exit (either by a call to
     _exit(2) or abnormally).

     vfork() returns 0 in the child's context and (later) the PID of the child
     in the parent's context.

RETURN VALUES
     Same as for fork(2).

SEE ALSO
     execve(2),  fork(2),  sigaction(2),  wait(2)

HISTORY
     The vfork() function call appeared in 2.9BSD.

BUGS
     To avoid a possible deadlock situation, processes that are children in
     the middle of a vfork() are never sent SIGTTOU or SIGTTIN signals;
     rather, output or ioctl(2) calls are allowed and input attempts result in
     an end-of-file indication.

OpenBSD 2.6                      June 30, 1997                               1

Source: OpenBSD 2.6 man pages. Copyright: Portions are copyrighted by BERKELEY
SOFTWARE DESIGN, INC., The Regents of the University of California, Massachusetts
Institute of Technology, Free Software Foundation, FreeBSD Inc., and others.



(Corrections, notes, and links courtesy of RocketAware.com)


[Detailed Topics]


[Overview Topics]

Up to: Process Signals and Events - Sending and handling signals and events.


RocketLink!--> Man page versions: OpenBSD FreeBSD NetBSD Solaris Others






Rapid-Links: Search | About | Comments | Submit Path: RocketAware > man pages > vfork.2/
RocketAware.com is a service of Mib Software
Copyright 1999, Forrest J. Cavalier III. All Rights Reserved.
We welcome submissions and comments