a6dacc2280
process with redirects. If we use vfork() and a redirect hangs (eg: opening a fifo) which the parent was intended to unhang, then the parent never gets to continue to unhang the child. eg: mkfifo f; cat <f &; echo foo>f The parent should not be waiting for a background process, even just for its exec() to complete. if there are no redirects there is (should be) nothing left that might be done that will cause any noticeable delay, so vfork() should be safe in all other cases. |
||
|---|---|---|
| .. | ||
| cat | ||
| chio | ||
| chmod | ||
| cp | ||
| csh | ||
| date | ||
| dd | ||
| df | ||
| domainname | ||
| echo | ||
| ed | ||
| expr | ||
| hostname | ||
| kill | ||
| ksh | ||
| ln | ||
| ls | ||
| mkdir | ||
| mt | ||
| mv | ||
| pax | ||
| ps | ||
| pwd | ||
| rcmd | ||
| rcp | ||
| rm | ||
| rmdir | ||
| sh | ||
| sleep | ||
| stty | ||
| sync | ||
| test | ||
| Makefile | ||
| Makefile.inc | ||