Date: Tue, 10 Sep 2002 10:52:58 -0700 (PDT) From: Nate Lawson <nate@root.org> To: Archie Cobbs <archie@dellroad.org> Cc: freebsd-arch@freebsd.org Subject: Re: /dev/stdout behavior Message-ID: <Pine.BSF.4.21.0209101051230.18643-100000@root.org> In-Reply-To: <200209101656.g8AGuJ433605@arch20m.dellroad.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 10 Sep 2002, Archie Cobbs wrote: > Is there an 'official' spec about how /dev/stdout is supposed to behave? > > 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. > grep FILENO /usr/include/unistd.h #define STDIN_FILENO 0 /* standard input file descriptor */ #define STDOUT_FILENO 1 /* standard output file descriptor */ #define STDERR_FILENO 2 /* standard error file descriptor */ -Nate 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?Pine.BSF.4.21.0209101051230.18643-100000>