Recent Features
| |||||||||||||
Fighting fork bombsFighting fork bombsPosted Apr 7, 2011 9:24 UTC (Thu) by renox (subscriber, #23785)In reply to: Fighting fork bombs by giraffedata Parent article: Fighting fork bombs
Currently when the parent exits its memory is totally freed, you're suggestion keeping the whole process until its children exits which can be expensive, maybe a middleground could be more useful ie keep only the 'identity' of the parent process and free the rest.
(Log in to post comments)
Fighting fork bombs Posted Apr 7, 2011 15:16 UTC (Thu) by giraffedata (subscriber, #1954) [Link] you're [suggesting] keeping the whole process until its children exits which can be expensive, maybe a middleground could be more useful ie keep only the 'identity' of the parent process and free the rest. I don't think "whole process" implies the program memory and I agree - if I were implementing this, I would have exit() free all the resources the process holds that aren't needed after the program is done running, as Linux does for zombie processes today. But like existing zombies, I would probably keep the whole task control block for simplicity.
|
|||||||||||||