diff options
| author | Christopher Faylor <me@cgf.cx> | 2004-12-05 05:30:20 +0300 |
|---|---|---|
| committer | Christopher Faylor <me@cgf.cx> | 2004-12-05 05:30:20 +0300 |
| commit | 3a72ce9d1248eb6e49647a4c431404ad2195385c (patch) | |
| tree | ae2507b4f5674eac23767c5d9a707dd17296dc41 /winsup/cygwin/how-vfork-works.txt | |
| parent | 8b6d072355d7858f044a3b077c09d35b00546934 (diff) | |
minor cleanup
Diffstat (limited to 'winsup/cygwin/how-vfork-works.txt')
| -rw-r--r-- | winsup/cygwin/how-vfork-works.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/winsup/cygwin/how-vfork-works.txt b/winsup/cygwin/how-vfork-works.txt index 7148366db..f249dab61 100644 --- a/winsup/cygwin/how-vfork-works.txt +++ b/winsup/cygwin/how-vfork-works.txt @@ -28,8 +28,8 @@ the result of a vfork and closes the extra file handles. This all relies on the fact that the child in a vfork call can affect just about everything in the parent except for the parent's fds. -The assumption is that a vfork is always just used as a method for
-starting a program.
+The assumption is that a vfork is always just used as a method for +starting a program. The assumption is also that all of this is much faster than the slow method that cygwin uses to implement fork(). |