Ken Hornstein <[email protected]> writes:
> I realize that dup2() clears the FD_CLOEXEC flag on the new file
> descriptor so the "normal" case of an opened file being dup2() down to 0
> would work correctly, but the wrinkle is that it does NOT if the old and
> new file descriptor are the same. That is admittedly unlikely, but it
> could happen in a few cases so I'd like to be as robust as possible.
But is that really an issue? It'd only occur if you're passing down
your own stdin, which presumably you inherited without FD_CLOEXEC.
regards, tom lane
--
nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers
