Differences between current version and revision by previous author of fchdir(2).
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 2 | Last edited on Thursday, October 31, 2002 8:53:50 pm | by PerryLorier | |
| Older page: | version 1 | Last edited on Tuesday, June 4, 2002 12:23:40 am | by perry | Revert |
@@ -1,138 +1,34 @@
-CHDIR
-!!!CHDIR
-NAME
-SYNOPSIS
-DESCRIPTION
-RETURN VALUE
-ERRORS
-NOTES
-CONFORMING TO
-SEE ALSO
-----
!!NAME
-
-
-chdir,
fchdir - change working directory
+fchdir - change working directory
!!SYNOPSIS
-__#include __
+
__#include <unistd.h>
__
-__int chdir(const char *__''path''__);
-
+
__int fchdir(int__ ''fd''__);__
!!DESCRIPTION
+__fchdir__ is identical to chdir(2), only that the directory is given as an open file descriptor.
-
-__chdir__ changes the current directory to that specified
-in ''path''.
-
-
-__fchdir__ is identical to __chdir__, only that the
-directory is given as an open file descriptor.
!!RETURN VALUE
+On success, zero is returned. On error, -1 is returned, and ''errno'' is set appropriately.
-
-On success, zero is returned. On error, -1 is returned, and
-''errno'' is set appropriately.
!!ERRORS
+Depending on the file system, other errors can be returned. The more general errors for fchdir(2) are listed below:
+;[ENOENT]: The file does not exist.
+;[ENOMEM]: Insufficient kernel memory was available.
+;[EIO]: An I/O error occurred.
+;[EBADF]: ''fd'' is not a valid file descriptor.
+;[EACCES]: Search permission was denied on the directory open on ''fd''.
-Depending on the file system, other errors can be returned.
-The more general errors for __chdir__ are listed
-below:
-
-
-__EFAULT__
-
-
-''path'' points outside your accessible address
-space.
-
-
-__ENAMETOOLONG__
-
-
-''path'' is too long.
-
-
-__ENOENT__
-
-
-The file does not exist.
-
-
-__ENOMEM__
-
-
-Insufficient kernel memory was available.
-
-
-__ENOTDIR__
-
-
-A component of ''path'' is not a directory.
-
-
-__EACCES__
-
-
-Search permission is denied on a component of
-''path''.
-
-
-__ELOOP__
-
-
-Too many symbolic links were encountered in resolving
-''path''.
-
-
-__EIO__
-
-
-An I/O error occurred.
-
-
-The general errors for __fchdir__ are listed
-below:
-
-
-__EBADF__
-
-
-''fd'' is not a valid file descriptor.
-
-
-__EACCES__
-
-
-Search permission was denied on the directory open on
-''fd''.
!!NOTES
+The prototype for fchdir(2) is only available if ___BSD_SOURCE__ is defined (either explicitly, or implicitly, by not defining _POSIX_SOURCE or compiling with the -ansi flag).
-The prototype for __fchdir__ is only available if
-___BSD_SOURCE__ is defined (either explicitly, or
-implicitly, by not defining _POSIX_SOURCE or compiling with
-the -ansi flag).
!!CONFORMING TO
+The fchdir(2) call is compatible with SVr4, 4.4BSD and X/OPEN. SVr4 documents additional [EIO], [EINTR], and [ENOLINK] error conditions. X/OPEN documents additional [EINTR] and [EIO] error conditions.
-The __chdir__ call is compatible with SVr4, SVID, POSIX,
-X/OPEN, 4.4BSD. SVr4 documents additional EINTR, ENOLINK,
-and EMULTIHOP error conditions but has no ENOMEM. POSIX.1
-does not have ENOMEM or ELOOP error conditions. X/OPEN does
-not have EFAULT, ENOMEM or EIO error
-conditions.
-
-
-The __fchdir__ call is compatible with SVr4, 4.4BSD and
-X/OPEN. SVr4 documents additional EIO, EINTR, and ENOLINK
-error conditions. X/OPEN documents additional EINTR and EIO
-error conditions.
!!SEE ALSO
-
-
getcwd(3), chroot(2)
-----
