Timeline for How do fork and exec work?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 20, 2015 at 0:21 | history | edited | psusi | CC BY-SA 3.0 | deleted 47 characters in body |
| Jan 18, 2015 at 19:22 | comment | added | John Kugelman | "For almost every command, the shell does a fork() so that the command runs in a new process. If that command is a builtin, then the child does not need to exec() a separate program." Good answer, but this part should be edited. The shell does not fork when running builtins. It runs those directly in the active shell process. This is the only way builtins like cd or read could work. The lack of forking also makes builtins much faster than external commands. | |
| Jan 18, 2015 at 6:24 | vote | accept | PriB | ||
| Jan 18, 2015 at 6:17 | vote | accept | PriB | ||
| Jan 18, 2015 at 6:17 | |||||
| Jan 17, 2015 at 22:37 | history | answered | psusi | CC BY-SA 3.0 |