Date: Tue, 10 Sep 2002 10:58:02 -0700 (PDT) From: Archie Cobbs <archie@dellroad.org> To: Bakul Shah <bakul@bitblocks.com> Cc: freebsd-arch@FreeBSD.ORG Subject: Re: /dev/stdout behavior Message-ID: <200209101758.g8AHw2C33935@arch20m.dellroad.org> In-Reply-To: <200209101717.NAA07504@wellington.cnchost.com> "from Bakul Shah at Sep 10, 2002 10:17:44 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Bakul Shah writes: > > 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. Arg, this whole time I meant to use '1' instead of '0'... But, hey-- now there's an even bigger bug! -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com 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?200209101758.g8AHw2C33935>