|
From: | Paul Eggert |
Subject: | bug#14752: [PATCH] sort: print warning when fork() failed for --compress-program |
Date: | Wed, 28 May 2014 09:22:44 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 |
Pádraig Brady wrote:
Anything where you need to interact with the sub process like setting up files to communicate etc. is going to have portability issues. Even using execvp() is problematic I understand.
As long as the child doesn't touch parent memory that the parent needs, it should be OK. There is a memory leak in execvp in old glibc versions, but I expect that isn't something we need to worry about.
Last time I checked, vfork was significantly faster than fork when the parent process has a lot of memory, and was still worth using for its performance advantages.
[Prev in Thread] | Current Thread | [Next in Thread] |