Petr Baudis <pasky@xxxxxx> writes:
> On Fri, Apr 05, 2013 at 11:57:19AM -0700, Junio C Hamano wrote:
> The thing is, I was confused about dup2() all along as my old UNIX
> masters taught me that I must close() the original descriptor first
> and since that's what's commonly done anyway, I never thought to
> double-check. Now I did and I learned something new, thanks!
Indeed, that's the crucial point here. dup2() is defined to close the
original FD first if needed.
It's much saner this way for the case of stderr, as there is no time
when we have no stderr available to report errors: the FD is replace
atomically from the POV of the program.
The manpage for dup2 does, however, say
If newfd was open, any errors that would have been reported at
close(2) time are lost. A careful programmer will not use dup2() or
dup3() without closing newfd first.
which is probably what you were referring to.
--
Thomas Rast
trast@{inf,student}.ethz.ch
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html