Date: Tue, 10 Sep 2002 10:17:44 -0700 From: Bakul Shah <bakul@bitblocks.com> To: Archie Cobbs <archie@dellroad.org> Cc: freebsd-arch@FreeBSD.ORG Subject: Re: /dev/stdout behavior Message-ID: <200209101717.NAA07504@wellington.cnchost.com> In-Reply-To: Your message of "Tue, 10 Sep 2002 09:56:19 PDT." <200209101656.g8AGuJ433605@arch20m.dellroad.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> For example, if you use fcntl() to set flags on fd 0, and then open > /dev/stdout, the new file descriptor you get back will have those > same flags set. Run the program below to see an example. This is > in agreement with the man page, which states that opening /dev/stdout > is equivalent to dup(2)'ing fd 0. Careful reading of man stdout will reveal that opening /dev/stdout is equivalent to dup()ing fd 1, not fd 0. FreeBSD has a bug. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200209101717.NAA07504>