Re:Fork() without exec() is dangerous in large programs (2016)
by mort96 on Tuesday June 14, 2022 @07:08PM
(#31747113)
Except that the set of things you are allowed to do after vfork() and before exec() is extremely small. I agree that things should use vfork or posix_spawn when possible, but it wouldn't surprise me at all if there's a similar list of cases when a vfork() path wouldn't be possible.
[ Parent
| on HN ]
Re:Fork() without exec() is dangerous in large programs (2016)
by cryptonector on Tuesday June 14, 2022 @07:11PM
(#31747142)
That set was made artificially small by the Open Group, but is not actually that small.