Re:Fork() without exec() is dangerous in large programs
by ej_campbell on Wednesday August 17, 2016 @03:29AM
(#12303014)
Only if your app is multi-threaded. Unfortunately, many apps are multi-threaded "under the covers" due to libraries that spawn threads, so you need to be careful.
This post does the best job explaining the issue: http://www.linuxprogrammingblog.com/threads-and-fork-think-t...
Re:Fork() without exec() is dangerous in large programs
by evanj on Wednesday August 17, 2016 @08:05AM
(#12304010)
This is possible, but I find these restrictions to be hard to follow. As soon as you need to call a function, you now need to audit that function to determine that it only calls other async signal safe functions. When you come back to the code to fix a bug six months later, you need to remember these restrictions.
Do this when you must, but it is easy to screw up.
Typically calls such as malloc(), printf() etc. are strictly forbidden in the child after a fork().