Re: lib/45148: dup2(3) and dup3(3) should support EINVAL

[Jukka Ruohonen <jruohonen%iki.fi@localhost>]

On Fri, Jul 15, 2011 at 10:50:44AM +0200, Martin Husemann wrote:
> On Fri, Jul 15, 2011 at 11:49:14AM +0300, Jukka Ruohonen wrote:
> > Yes, however dup3(2) is not standardized, AFAIR, leaving the behavior
> > "undefined". And the case (a) should still apply.
> 
> Yes, I was only meaning to disaprove on applying case (b) to dup2.

From a quick look, there is also a small defect in the manual page: how can
dup2(2) or dup3(2) ever fail with EMFILE? (Also SUSv4 omits this for dup2(2).)