NetBSD/bin/sh
kre a6dacc2280 Use fork() rather than vfork() when forking to run a background
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.
2019-12-21 18:54:15 +00:00
..
USD.doc
bltin
funcs
Makefile
TOUR
alias.c
alias.h
arith_token.c
arith_tokens.h
arithmetic.c
arithmetic.h
builtins.def
cd.c
cd.h
error.c
error.h
eval.c Use fork() rather than vfork() when forking to run a background 2019-12-21 18:54:15 +00:00
eval.h
exec.c
exec.h
expand.c
expand.h
histedit.c
init.h
input.c
input.h
jobs.c
jobs.h
machdep.h
mail.c
mail.h
main.c
main.h
memalloc.c
memalloc.h
miscbltin.c
miscbltin.h
mkbuiltins
mkinit.sh
mknodenames.sh
mknodes.sh
mkoptions.sh
mktokens
myhistedit.h
mystring.c
mystring.h
nodes.c.pat
nodetypes
option.list
options.c
options.h
output.c
output.h
parser.c Correct a typo in a comment, 08x0 was meant to be 0x80 (duh!). NFC. 2019-12-10 09:18:37 +00:00
parser.h
redir.c
redir.h
sh.1
shell.h
show.c
show.h
syntax.c
syntax.h
trap.c
trap.h
var.c
var.h
version.h