On 05/13/2014 12:12 PM, niXman wrote:
I'm curious whether there is reason to use 'vfork()' rather than 'fork()'?
Without memory overcommitment, fork needs physical backing storage (RAM or swap) for all copy-on-write pages in the new process. vfork doesn't.
-- Florian Weimer / Red Hat Product Security Team
