int dup(int fildes);
int dup2(int fildes, int fildes2);
The dup() and dup2() functions provide an alternative interface to the service provided by fcntl() using the F_DUPFD command. The call:
fid = dup(fildes);
shall be equivalent to:
fid = fcntl(fildes, F_DUPFD, 0);
fid = dup2(fildes, fildes2);
shall be equivalent to:
close(fildes2); fid = fcntl(fildes, F_DUPFD, fildes2);
except for the following:
Upon successful completion a non-negative integer, namely the file descriptor, shall be returned; otherwise, -1 shall be returned and errno set to indicate the error.
The dup() function shall fail if:
The dup2() function shall fail if:
The following sections are informative.
The following example closes standard output for the current processes, re-assigns standard output to go to the file referenced by pfd, and closes the original file descriptor to clean up.
#include <unistd.h> ... int pfd; ... close(1); dup(pfd); close(pfd); ...
The following example redirects messages from stderr to stdout.
#include <unistd.h> ... dup2(1, 2); ...
The dup() and dup2() functions are redundant. Their services are also provided by the fcntl() function. They have been included in this volume of IEEE Std 1003.1-2001 primarily for historical reasons, since many existing applications use them.
While the brief code segment shown is very similar in behavior to dup2(), a conforming implementation based on other functions defined in this volume of IEEE Std 1003.1-2001 is significantly more complex. Least obvious is the possible effect of a signal-catching function that could be invoked between steps and allocate or deallocate file descriptors. This could be avoided by blocking signals.
The dup2() function is not marked obsolescent because it presents a type-safe version of functionality provided in a type-unsafe version by fcntl(). It is used in the POSIX Ada binding.
The dup2() function is not intended for use in critical regions as a synchronization mechanism.
In the description of [EBADF], the case of fildes being out of range is covered by the given case of fildes not being valid. The descriptions for fildes and fildes2 are different because the only kind of invalidity that is relevant for fildes2 is whether it is out of range; that is, it does not matter whether fildes2 refers to an open file when the dup2() call is made.
close() , fcntl() , open() , the Base Definitions volume of IEEE Std 1003.1-2001, <unistd.h>