Timeline for Is recursive forking considered an anti-pattern?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 25, 2011 at 11:35 | vote | accept | Nathan Long | ||
| Dec 25, 2011 at 11:34 | comment | added | Nathan Long | @JoeyAdams - LOL. Well played, sir. | |
| Dec 25, 2011 at 10:32 | answer | added | Bill Michell | timeline score: 7 | |
| Dec 25, 2011 at 9:49 | answer | added | Cybercartel | timeline score: 0 | |
| Dec 25, 2011 at 4:25 | comment | added | Joey Adams | I'm firing a shotgun, and noticed my foot is starting to bleed. Is this dangerous? | |
| Dec 24, 2011 at 20:41 | comment | added | user4459 | A recursive fork is a sort of denial of service aka fork bomb. | |
| Dec 24, 2011 at 16:39 | comment | added | Job | After the fork runs there is a return flag of some sort which can tell you whether you are the parent or the newly born clone. I think it is OK to fork in a loop, as long as only the parent does so. In the movie "The 6th day" they looked inside the eye to figure out if the person was a clone. There is a similar but different way of doing this in C. The important thing is: you must have precise control over who forks and who does not. Otherwise you cannot reason about what is going on in your multi-process code. | |
| Dec 24, 2011 at 16:30 | history | asked | Nathan Long | CC BY-SA 3.0 |