Re: sh(1) exec redirection

> Yes, that is exactly the issue, we want

> 	exec 3>whatever

> to set close-on-exec (by default) as typically fds created that way
> are just for the script to use, and shouldn't be passed through to
> children.

We do?  Perhaps if this were just being designed now.  But breaking
existing use cases strikes me as a Very Bad Idea.  I think that,
instead, some way should have been designed to set CLOEXEC _without_
breaking existing use cases.

Is this what the fdflags you mentioned is?  If so, shouldn't the
CLOEXEC misfeature be rolled back, since there's a now way to get that
effect that's compatible with decades of history?

/~\ The ASCII				  Mouse
\ / Ribbon Campaign
 X  Against HTML		[email protected]
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B