From: Alejandro Colomar Date: Sun, 30 Mar 2025 19:00:40 +0000 (+0200) Subject: man/: Use 'path' instead of 'pathname' for parameters X-Git-Tag: man-pages-6.14~37 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=f456d8a11bab6851c18fa9902731978aa2083588;p=thirdparty%2Fman-pages.git man/: Use 'path' instead of 'pathname' for parameters It's just as informative, and takes less space. Signed-off-by: Alejandro Colomar --- diff --git a/man/man2/access.2 b/man/man2/access.2 index 5f9dede7b..1b1fe80ac 100644 --- a/man/man2/access.2 +++ b/man/man2/access.2 @@ -30,13 +30,13 @@ Standard C library .nf .B #include .P -.BI "int access(const char *" pathname ", int " mode ); +.BI "int access(const char *" path ", int " mode ); .P .BR "#include " " /* Definition of " AT_* " constants */" .B #include .P -.BI "int faccessat(int " dirfd ", const char *" pathname ", int " \ -mode ", int " flags ); +.BI "int faccessat(int " dirfd ", const char *" path ", int " mode \ +", int " flags ); /* But see C library/kernel differences, below */ .P .BR "#include " " /* Definition of " AT_* " constants */" @@ -44,7 +44,7 @@ mode ", int " flags ); .B #include .P .B int syscall(SYS_faccessat2, -.BI " int " dirfd ", const char *" pathname ", int " mode \ +.BI " int " dirfd ", const char *" path ", int " mode \ ", int " flags ); .fi .P @@ -63,9 +63,9 @@ Feature Test Macro Requirements for glibc (see .SH DESCRIPTION .BR access () checks whether the calling process can access the file -.IR pathname . +.IR path . If -.I pathname +.I path is a symbolic link, it is dereferenced. .P The @@ -117,8 +117,8 @@ operates in exactly the same way as .BR access (), except for the differences described here. .P -If the pathname given in -.I pathname +If +.I path is relative, then it is interpreted relative to the directory referred to by the file descriptor .I dirfd @@ -128,19 +128,19 @@ the calling process, as is done by for a relative pathname). .P If -.I pathname +.I path is relative and .I dirfd is the special value .BR AT_FDCWD , then -.I pathname +.I path is interpreted relative to the current working directory of the calling process (like .BR access ()). .P If -.I pathname +.I path is absolute, then .I dirfd is ignored. @@ -157,7 +157,7 @@ uses the real IDs (like .TP .BR AT_EMPTY_PATH " (since Linux 5.8)" If -.I pathname +.I path is an empty string, operate on the file referred to by .I dirfd (which may have been obtained using the @@ -178,7 +178,7 @@ to obtain its definition. .TP .B AT_SYMLINK_NOFOLLOW If -.I pathname +.I path is a symbolic link, do not dereference it: instead return information about the link itself. .P @@ -226,13 +226,13 @@ is set to indicate the error. .B EACCES The requested access would be denied to the file, or search permission is denied for one of the directories in the path prefix of -.IR pathname . +.IR path . (See also .BR path_resolution (7).) .TP .B EBADF .RB ( faccessat ()) -.I pathname +.I path is relative but .I dirfd is neither @@ -241,7 +241,7 @@ is neither nor a valid file descriptor. .TP .B EFAULT -.I pathname +.I path points outside your accessible address space. .TP .B EINVAL @@ -258,15 +258,15 @@ An I/O error occurred. .TP .B ELOOP Too many symbolic links were encountered in resolving -.IR pathname . +.IR path . .TP .B ENAMETOOLONG -.I pathname +.I path is too long. .TP .B ENOENT A component of -.I pathname +.I path does not exist or is a dangling symbolic link. .TP .B ENOMEM @@ -274,12 +274,12 @@ Insufficient kernel memory was available. .TP .B ENOTDIR A component used as a directory in -.I pathname +.I path is not, in fact, a directory. .TP .B ENOTDIR .RB ( faccessat ()) -.I pathname +.I path is relative and .I dirfd is a file descriptor referring to a file other than a directory. @@ -328,8 +328,8 @@ flags are not specified), the glibc wrapper function falls back to the use of .BR access (). When -.I pathname -is a relative pathname, +.I path +is relative, glibc constructs a pathname based on the symbolic link in .I /proc/self/fd that corresponds to the @@ -383,7 +383,7 @@ are permitted. .P A file is accessible only if the permissions on each of the directories in the path prefix of -.I pathname +.I path grant search (i.e., execute) access. If any directory is inaccessible, then the .BR access () diff --git a/man/man2/chmod.2 b/man/man2/chmod.2 index ae53fe3c9..c95c34f9c 100644 --- a/man/man2/chmod.2 +++ b/man/man2/chmod.2 @@ -19,13 +19,13 @@ Standard C library .nf .B #include .P -.BI "int chmod(const char *" pathname ", mode_t " mode ); +.BI "int chmod(const char *" path ", mode_t " mode ); .BI "int fchmod(int " fd ", mode_t " mode ); .P .BR "#include " " /* Definition of AT_* constants */" .B #include .P -.BI "int fchmodat(int " dirfd ", const char *" pathname ", mode_t " \ +.BI "int fchmodat(int " dirfd ", const char *" path ", mode_t " \ mode ", int " flags ); .fi .P @@ -70,7 +70,7 @@ These system calls differ only in how the file is specified: .IP \[bu] 3 .BR chmod () changes the mode of the file specified whose pathname is given in -.IR pathname , +.IR path , which is dereferenced if it is a symbolic link. .IP \[bu] .BR fchmod () @@ -168,8 +168,8 @@ system call operates in exactly the same way as .BR chmod (), except for the differences described here. .P -If the pathname given in -.I pathname +If +.I path is relative, then it is interpreted relative to the directory referred to by the file descriptor .I dirfd @@ -179,19 +179,19 @@ the calling process, as is done by for a relative pathname). .P If -.I pathname +.I path is relative and .I dirfd is the special value .BR AT_FDCWD , then -.I pathname +.I path is interpreted relative to the current working directory of the calling process (like .BR chmod ()). .P If -.I pathname +.I path is absolute, then .I dirfd is ignored. @@ -201,7 +201,7 @@ can either be 0, or include the following flag: .TP .B AT_SYMLINK_NOFOLLOW If -.I pathname +.I path is a symbolic link, do not dereference it: instead operate on the link itself. This flag is not currently implemented. @@ -236,7 +236,7 @@ is not valid. .TP .B EBADF .RB ( fchmodat ()) -.I pathname +.I path is relative but .I dirfd is neither @@ -244,7 +244,7 @@ is neither nor a valid file descriptor. .TP .B EFAULT -.I pathname +.I path points outside your accessible address space. .TP .B EINVAL @@ -257,10 +257,10 @@ An I/O error occurred. .TP .B ELOOP Too many symbolic links were encountered in resolving -.IR pathname . +.IR path . .TP .B ENAMETOOLONG -.I pathname +.I path is too long. .TP .B ENOENT @@ -274,7 +274,7 @@ A component of the path prefix is not a directory. .TP .B ENOTDIR .RB ( fchmodat ()) -.I pathname +.I path is relative and .I dirfd is a file descriptor referring to a file other than a directory. @@ -316,7 +316,7 @@ On older kernels where is unavailable, the glibc wrapper function falls back to the use of .BR chmod (). When -.I pathname +.I path is a relative pathname, glibc constructs a pathname based on the symbolic link in .I /proc/self/fd diff --git a/man/man2/chown.2 b/man/man2/chown.2 index 3d85bf23f..9bdbf1832 100644 --- a/man/man2/chown.2 +++ b/man/man2/chown.2 @@ -25,14 +25,14 @@ Standard C library .nf .B #include .P -.BI "int chown(const char *" pathname ", uid_t " owner ", gid_t " group ); +.BI "int chown(const char *" path ", uid_t " owner ", gid_t " group ); .BI "int fchown(int " fd ", uid_t " owner ", gid_t " group ); -.BI "int lchown(const char *" pathname ", uid_t " owner ", gid_t " group ); +.BI "int lchown(const char *" path ", uid_t " owner ", gid_t " group ); .P .BR "#include " "/* Definition of AT_* constants */" .B #include .P -.BI "int fchownat(int " dirfd ", const char *" pathname , +.BI "int fchownat(int " dirfd ", const char *" path , .BI " uid_t " owner ", gid_t " group ", int " flags ); .fi .P @@ -68,7 +68,7 @@ system calls differ only in how the file is specified: .IP \[bu] 3 .BR chown () changes the ownership of the file specified by -.IR pathname , +.IR path , which is dereferenced if it is a symbolic link. .IP \[bu] .BR fchown () @@ -126,8 +126,8 @@ system call operates in exactly the same way as .BR chown (), except for the differences described here. .P -If the pathname given in -.I pathname +If +.I path is relative, then it is interpreted relative to the directory referred to by the file descriptor .I dirfd @@ -137,19 +137,19 @@ the calling process, as is done by for a relative pathname). .P If -.I pathname +.I path is relative and .I dirfd is the special value .BR AT_FDCWD , then -.I pathname +.I path is interpreted relative to the current working directory of the calling process (like .BR chown ()). .P If -.I pathname +.I path is absolute, then .I dirfd is ignored. @@ -162,7 +162,7 @@ argument is a bit mask created by ORing together .BR AT_EMPTY_PATH " (since Linux 2.6.39)" .\" commit 65cfc6722361570bfe255698d9cd4dccaf47570d If -.I pathname +.I path is an empty string, operate on the file referred to by .I dirfd (which may have been obtained using the @@ -184,7 +184,7 @@ to obtain its definition. .TP .B AT_SYMLINK_NOFOLLOW If -.I pathname +.I path is a symbolic link, do not dereference it: instead operate on the link itself, like .BR lchown (). @@ -222,7 +222,7 @@ is not a valid open file descriptor. .TP .B EBADF .RB ( fchownat ()) -.I pathname +.I path is relative but .I dirfd is neither @@ -230,7 +230,7 @@ is neither nor a valid file descriptor. .TP .B EFAULT -.I pathname +.I path points outside your accessible address space. .TP .B EINVAL @@ -244,10 +244,10 @@ A low-level I/O error occurred while modifying the inode. .TP .B ELOOP Too many symbolic links were encountered in resolving -.IR pathname . +.IR path . .TP .B ENAMETOOLONG -.I pathname +.I path is too long. .TP .B ENOENT @@ -261,7 +261,7 @@ A component of the path prefix is not a directory. .TP .B ENOTDIR .RB ( fchownat ()) -.I pathname +.I path is relative and .I dirfd is a file descriptor referring to a file other than a directory. @@ -359,8 +359,8 @@ is unavailable, the glibc wrapper function falls back to the use of and .BR lchown (). When -.I pathname -is a relative pathname, +.I path +is relative, glibc constructs a pathname based on the symbolic link in .I /proc/self/fd that corresponds to the diff --git a/man/man2/execve.2 b/man/man2/execve.2 index 92fecda65..7b14b5cf1 100644 --- a/man/man2/execve.2 +++ b/man/man2/execve.2 @@ -24,18 +24,18 @@ Standard C library .nf .B #include .P -.BI "int execve(const char *" pathname ", char *const _Nullable " argv [], +.BI "int execve(const char *" path ", char *const _Nullable " argv [], .BI " char *const _Nullable " envp []); .fi .SH DESCRIPTION .BR execve () executes the program referred to by -.IR pathname . +.IR path . This causes the program that is currently being run by the calling process to be replaced with a new program, with newly initialized stack, heap, and (initialized and uninitialized) data segments. .P -.I pathname +.I path must be either a binary executable, or a script starting with a line of the form: .P @@ -105,7 +105,7 @@ after a successful .BR execve (). .P If the set-user-ID bit is set on the program file referred to by -.IR pathname , +.IR path , then the effective user ID of the calling process is changed to that of the owner of the program file. Similarly, if the set-group-ID bit is set on the program file, @@ -337,7 +337,7 @@ will be invoked with the following arguments: .in +4n .SY \f[I]interpreter\f[] .RI [ optional-arg ] -.I pathname +.I path .IR arg ... .YS .in @@ -446,13 +446,13 @@ and argument list is too large, an argument or environment string is too long, or the full -.I pathname +.I path of the executable is too long. The terminating null byte is counted as part of the string length. .TP .B EACCES Search permission is denied on a component of the path prefix of -.I pathname +.I path or the name of a script interpreter. (See also .BR path_resolution (7).) @@ -478,7 +478,7 @@ resource limit (see For a more detailed explanation of this error, see NOTES. .TP .B EFAULT -.I pathname +.I path or one of the pointers in the vectors .I argv or @@ -500,7 +500,7 @@ An ELF interpreter was not in a recognized format. .TP .B ELOOP Too many symbolic links were encountered in resolving -.I pathname +.I path or the name of a script or ELF interpreter. .TP .B ELOOP @@ -515,15 +515,14 @@ the error produced for this case was The per-process limit on the number of open file descriptors has been reached. .TP .B ENAMETOOLONG -.I pathname +.I path is too long. .TP .B ENFILE The system-wide limit on the total number of open files has been reached. .TP .B ENOENT -The file -.I pathname +.I path or a script or ELF interpreter does not exist. .TP .B ENOEXEC @@ -536,7 +535,7 @@ Insufficient kernel memory was available. .TP .B ENOTDIR A component of the path prefix of -.I pathname +.I path or a script or ELF interpreter is not a directory. .TP .B EPERM diff --git a/man/man2/execveat.2 b/man/man2/execveat.2 index 5ad3128c0..474c2c39d 100644 --- a/man/man2/execveat.2 +++ b/man/man2/execveat.2 @@ -14,7 +14,7 @@ Standard C library .BR "#include " " /* Definition of " AT_* " constants */" .B #include .P -.BI "int execveat(int " dirfd ", const char *" pathname , +.BI "int execveat(int " dirfd ", const char *" path , .BI " char *const _Nullable " argv [], .BI " char *const _Nullable " envp [], .BI " int " flags ); @@ -26,13 +26,13 @@ The system call executes the program referred to by the combination of .I dirfd and -.IR pathname . +.IR path . It operates in exactly the same way as .BR execve (2), except for the differences described in this manual page. .P -If the pathname given in -.I pathname +If +.I path is relative, then it is interpreted relative to the directory referred to by the file descriptor .I dirfd @@ -42,25 +42,25 @@ the calling process, as is done by for a relative pathname). .P If -.I pathname +.I path is relative and .I dirfd is the special value .BR AT_FDCWD , then -.I pathname +.I path is interpreted relative to the current working directory of the calling process (like .BR execve (2)). .P If -.I pathname +.I path is absolute, then .I dirfd is ignored. .P If -.I pathname +.I path is an empty string and the .B AT_EMPTY_PATH flag is specified, then the file descriptor @@ -75,7 +75,7 @@ argument is a bit mask that can include zero or more of the following flags: .TP .B AT_EMPTY_PATH If -.I pathname +.I path is an empty string, operate on the file referred to by .I dirfd (which may have been obtained using the @@ -87,7 +87,7 @@ flag). If the file identified by .I dirfd and a non-NULL -.I pathname +.I path is a symbolic link, then the call fails with the error .BR ELOOP . .SH RETURN VALUE @@ -105,7 +105,7 @@ can also occur for The following additional errors can occur for .BR execveat (): .TP -.I pathname +.I path is relative but .I dirfd is neither @@ -123,14 +123,14 @@ includes and the file identified by .I dirfd and a non-NULL -.I pathname +.I path is a symbolic link. .TP .B ENOENT The program identified by .I dirfd and -.I pathname +.I path requires the use of an interpreter program (such as a script starting with "#!"), but the file descriptor .I dirfd @@ -141,7 +141,7 @@ the program file is inaccessible to the launched interpreter. See BUGS. .TP .B ENOTDIR -.I pathname +.I path is relative and .I dirfd is a file descriptor referring to a file other than a directory. @@ -178,11 +178,11 @@ is employed. A string of the second form occurs when the script is specified via both .I dirfd and -.IR pathname ; +.IR path ; in this case, .I P is the value given in -.IR pathname . +.IR path . .P For the same reasons described in .BR fexecve (3), diff --git a/man/man2/fanotify_mark.2 b/man/man2/fanotify_mark.2 index 47cafb21c..15e748b63 100644 --- a/man/man2/fanotify_mark.2 +++ b/man/man2/fanotify_mark.2 @@ -14,7 +14,7 @@ Standard C library .P .BI "int fanotify_mark(int " fanotify_fd ", unsigned int " flags , .BI " uint64_t " mask ", int " dirfd , -.BI " const char *_Nullable " pathname ); +.BI " const char *_Nullable " path ); .fi .SH DESCRIPTION For an overview of the fanotify API, see @@ -85,13 +85,13 @@ zero or more of the following values may be ORed into .TP .B FAN_MARK_DONT_FOLLOW If -.I pathname +.I path is a symbolic link, mark the link itself, rather than the file to which it refers. (By default, .BR fanotify_mark () dereferences -.I pathname +.I path if it is a symbolic link.) .TP .B FAN_MARK_ONLYDIR @@ -101,11 +101,11 @@ shall be raised. .TP .B FAN_MARK_MOUNT Mark the mount specified by -.IR pathname . +.IR path . If -.I pathname +.I path is not itself a mount point, the mount containing -.I pathname +.I path will be marked. All directories, subdirectories, and the contained files of the mount will be monitored. @@ -132,9 +132,9 @@ capability. .BR FAN_MARK_FILESYSTEM " (since Linux 4.20)" .\" commit d54f4fba889b205e9cd8239182ca5d27d0ac3bc2 Mark the filesystem specified by -.IR pathname . +.IR path . The filesystem containing -.I pathname +.I path will be marked. All the contained files and directories of the filesystem from any mount point will be monitored. @@ -500,16 +500,16 @@ A file or directory has been moved The filesystem object to be marked is determined by the file descriptor .I dirfd and the pathname specified in -.IR pathname : +.IR path : .IP \[bu] 3 If -.I pathname +.I path is NULL, .I dirfd defines the filesystem object to be marked. .IP \[bu] If -.I pathname +.I path is NULL, and .I dirfd takes the special value @@ -517,30 +517,30 @@ takes the special value the current working directory is to be marked. .IP \[bu] If -.I pathname +.I path is absolute, it defines the filesystem object to be marked, and .I dirfd is ignored. .IP \[bu] If -.I pathname +.I path is relative, and .I dirfd does not have the value .BR AT_FDCWD , then the filesystem object to be marked is determined by interpreting -.I pathname +.I path relative the directory referred to by .IR dirfd . .IP \[bu] If -.I pathname +.I path is relative, and .I dirfd has the value .BR AT_FDCWD , then the filesystem object to be marked is determined by interpreting -.I pathname +.I path relative to the current working directory. (See .BR openat (2) @@ -561,7 +561,7 @@ An invalid file descriptor was passed in .IR fanotify_fd . .TP .B EBADF -.I pathname +.I path is relative but .I dirfd is neither @@ -572,7 +572,7 @@ nor a valid file descriptor. The filesystem object indicated by .I dirfd and -.I pathname +.I path has a mark that was updated without the .B FAN_MARK_EVICTABLE flag, @@ -584,7 +584,7 @@ flag. The filesystem object indicated by .I dirfd and -.I pathname +.I path has a mark that was updated with the .B FAN_MARK_IGNORE flag, @@ -596,7 +596,7 @@ flag. The filesystem object indicated by .I dirfd and -.I pathname +.I path has a mark that was updated with the .B FAN_MARK_IGNORE and @@ -651,14 +651,14 @@ but does not contain and .I dirfd and -.I pathname +.I path specify a directory. .TP .B ENODEV The filesystem object indicated by .I dirfd and -.I pathname +.I path is associated with a filesystem that reports zero .I fsid (e.g., @@ -674,7 +674,7 @@ when trying to add a mount or filesystem mark. The filesystem object indicated by .I dirfd and -.I pathname +.I path does not exist. This error also occurs when trying to remove a mark from an object which is not marked. @@ -704,7 +704,7 @@ contains and .I dirfd and -.I pathname +.I path do not specify a directory. .TP .B ENOTDIR @@ -714,7 +714,7 @@ contains and .I dirfd and -.I pathname +.I path do not specify a directory. .TP .B ENOTDIR @@ -736,12 +736,12 @@ or directory event flags and .I dirfd and -.I pathname +.I path do not specify a directory. .TP .B EOPNOTSUPP The object indicated by -.I pathname +.I path is associated with a filesystem that does not support the encoding of file handles. This error can be returned only with an fanotify group that identifies @@ -759,7 +759,7 @@ The operation is not permitted because the caller lacks a required capability. .TP .B EXDEV The filesystem object indicated by -.I pathname +.I path resides within a filesystem subvolume (e.g., .BR btrfs (5)) which uses a different @@ -844,7 +844,7 @@ contains .BR FAN_MARK_FLUSH , .IR dirfd , and -.I pathname +.I path must specify a valid filesystem object, even though this object is not used. .IP \[bu] .\" Fixed by commit d4c7cf6cffb1bc711a833b5e304ba5bcfe76398b diff --git a/man/man2/futimesat.2 b/man/man2/futimesat.2 index 309ab0baa..a8e649383 100644 --- a/man/man2/futimesat.2 +++ b/man/man2/futimesat.2 @@ -14,7 +14,7 @@ Standard C library .BR "#include " " /* Definition of " AT_* " constants */" .B #include .P -.BI "[[deprecated]] int futimesat(int " dirfd ", const char *" pathname , +.BI "[[deprecated]] int futimesat(int " dirfd ", const char *" path , .BI " const struct timeval " times [2]); .fi .P @@ -39,8 +39,8 @@ system call operates in exactly the same way as .BR utimes (2), except for the differences described in this manual page. .P -If the pathname given in -.I pathname +If +.I path is relative, then it is interpreted relative to the directory referred to by the file descriptor .I dirfd @@ -50,19 +50,19 @@ the calling process, as is done by for a relative pathname). .P If -.I pathname +.I path is relative and .I dirfd is the special value .BR AT_FDCWD , then -.I pathname +.I path is interpreted relative to the current working directory of the calling process (like .BR utimes (2)). .P If -.I pathname +.I path is absolute, then .I dirfd is ignored. @@ -87,7 +87,7 @@ The following additional errors can occur for .BR futimesat (): .TP .B EBADF -.I pathname +.I path is relative but .I dirfd is neither @@ -95,14 +95,14 @@ is neither nor a valid file descriptor. .TP .B ENOTDIR -.I pathname +.I path is relative and .I dirfd is a file descriptor referring to a file other than a directory. .SH VERSIONS .SS glibc If -.I pathname +.I path is NULL, then the glibc .BR futimesat () wrapper function updates the times for the file referred to by diff --git a/man/man2/inotify_add_watch.2 b/man/man2/inotify_add_watch.2 index 02ddd49e5..999dae4d5 100644 --- a/man/man2/inotify_add_watch.2 +++ b/man/man2/inotify_add_watch.2 @@ -16,20 +16,20 @@ Standard C library .nf .B #include .P -.BI "int inotify_add_watch(int " fd ", const char *" pathname ", uint32_t " mask ); +.BI "int inotify_add_watch(int " fd ", const char *" path ", uint32_t " mask ); .fi .SH DESCRIPTION .BR inotify_add_watch () adds a new watch, or modifies an existing watch, for the file whose location is specified in -.IR pathname ; +.IR path ; the caller must have read permission for this file. The .I fd argument is a file descriptor referring to the inotify instance whose watch list is to be modified. The events to be monitored for -.I pathname +.I path are specified in the .I mask bit-mask argument. @@ -42,7 +42,7 @@ A successful call to .BR inotify_add_watch () returns a unique watch descriptor for this inotify instance, for the filesystem object (inode) that corresponds to -.IR pathname . +.IR path . If the filesystem object was not previously being watched by this inotify instance, then the watch descriptor is newly allocated. @@ -80,12 +80,12 @@ The given file descriptor is not valid. contains .B IN_MASK_CREATE and -.I pathname +.I path refers to a file already being watched by the same .IR fd . .TP .B EFAULT -.I pathname +.I path points outside of the process's accessible address space. .TP .B EINVAL @@ -100,12 +100,12 @@ or is not an inotify file descriptor. .TP .B ENAMETOOLONG -.I pathname +.I path is too long. .TP .B ENOENT A directory component in -.I pathname +.I path does not exist or is a dangling symbolic link. .TP .B ENOMEM @@ -120,7 +120,7 @@ kernel failed to allocate a needed resource. contains .B IN_ONLYDIR and -.I pathname +.I path is not a directory. .SH STANDARDS Linux. diff --git a/man/man2/mkdir.2 b/man/man2/mkdir.2 index 20163c88e..d55647f9e 100644 --- a/man/man2/mkdir.2 +++ b/man/man2/mkdir.2 @@ -16,12 +16,12 @@ Standard C library .B #include .\" .B #include .P -.BI "int mkdir(const char *" pathname ", mode_t " mode ); +.BI "int mkdir(const char *" path ", mode_t " mode ); .P .BR "#include " "/* Definition of AT_* constants */" .B #include .P -.BI "int mkdirat(int " dirfd ", const char *" pathname ", mode_t " mode ); +.BI "int mkdirat(int " dirfd ", const char *" path ", mode_t " mode ); .fi .P .RS -4 @@ -39,7 +39,7 @@ Feature Test Macro Requirements for glibc (see .SH DESCRIPTION .BR mkdir () attempts to create a directory named -.IR pathname . +.IR path . .P The argument .I mode @@ -76,8 +76,8 @@ system call operates in exactly the same way as .BR mkdir (), except for the differences described here. .P -If the pathname given in -.I pathname +If +.I path is relative, then it is interpreted relative to the directory referred to by the file descriptor .I dirfd @@ -87,19 +87,19 @@ the calling process, as is done by for a relative pathname). .P If -.I pathname +.I path is relative and .I dirfd is the special value .BR AT_FDCWD , then -.I pathname +.I path is interpreted relative to the current working directory of the calling process (like .BR mkdir ()). .P If -.I pathname +.I path is absolute, then .I dirfd is ignored. @@ -121,14 +121,14 @@ is set to indicate the error. .B EACCES The parent directory does not allow write permission to the process, or one of the directories in -.I pathname +.I path did not allow search permission. (See also .BR path_resolution (7).) .TP .B EBADF .RB ( mkdirat ()) -.I pathname +.I path is relative but .I dirfd is neither @@ -140,35 +140,37 @@ The user's quota of disk blocks or inodes on the filesystem has been exhausted. .TP .B EEXIST -.I pathname +.I path already exists (not necessarily as a directory). This includes the case where -.I pathname +.I path is a symbolic link, dangling or not. .TP .B EFAULT -.IR pathname " points outside your accessible address space." +.I path +points outside your accessible address space. .TP .B EINVAL The final component ("basename") of the new directory's -.I pathname +.I path is invalid (e.g., it contains characters not permitted by the underlying filesystem). .TP .B ELOOP Too many symbolic links were encountered in resolving -.IR pathname . +.IR path . .TP .B EMLINK The number of links to the parent directory would exceed .BR LINK_MAX . .TP .B ENAMETOOLONG -.IR pathname " was too long." +.I path +was too long. .TP .B ENOENT A directory component in -.I pathname +.I path does not exist or is a dangling symbolic link. .TP .B ENOMEM @@ -176,7 +178,7 @@ Insufficient kernel memory was available. .TP .B ENOSPC The device containing -.I pathname +.I path has no room for the new directory. .TP .B ENOSPC @@ -185,23 +187,23 @@ exhausted. .TP .B ENOTDIR A component used as a directory in -.I pathname +.I path is not, in fact, a directory. .TP .B ENOTDIR .RB ( mkdirat ()) -.I pathname +.I path is relative and .I dirfd is a file descriptor referring to a file other than a directory. .TP .B EPERM The filesystem containing -.I pathname +.I path does not support the creation of directories. .TP .B EROFS -.I pathname +.I path refers to a file on a read-only filesystem. .TP .B EOVERFLOW @@ -219,8 +221,8 @@ On older kernels where is unavailable, the glibc wrapper function falls back to the use of .BR mkdir (). When -.I pathname -is a relative pathname, +.I path +is relative, glibc constructs a pathname based on the symbolic link in .I /proc/self/fd that corresponds to the diff --git a/man/man2/mknod.2 b/man/man2/mknod.2 index eda290adc..aec5908f3 100644 --- a/man/man2/mknod.2 +++ b/man/man2/mknod.2 @@ -19,12 +19,12 @@ Standard C library .nf .B #include .P -.BI "int mknod(const char *" pathname ", mode_t " mode ", dev_t " dev ); +.BI "int mknod(const char *" path ", mode_t " mode ", dev_t " dev ); .P .BR "#include " "/* Definition of AT_* constants */" .B #include .P -.BI "int mknodat(int " dirfd ", const char *" pathname ", mode_t " mode \ +.BI "int mknodat(int " dirfd ", const char *" path ", mode_t " mode \ ", dev_t " dev ); .fi .P @@ -45,7 +45,7 @@ The system call .BR mknod () creates a filesystem node (file, device special file, or named pipe) named -.IR pathname , +.IR path , with attributes specified by .I mode and @@ -93,7 +93,7 @@ may be useful to build the value for otherwise it is ignored. .P If -.I pathname +.I path already exists, or is a symbolic link, this call fails with an .B EEXIST error. @@ -113,8 +113,8 @@ system call operates in exactly the same way as .BR mknod (), except for the differences described here. .P -If the pathname given in -.I pathname +If +.I path is relative, then it is interpreted relative to the directory referred to by the file descriptor .I dirfd @@ -124,19 +124,19 @@ the calling process, as is done by for a relative pathname). .P If -.I pathname +.I path is relative and .I dirfd is the special value .BR AT_FDCWD , then -.I pathname +.I path is interpreted relative to the current working directory of the calling process (like .BR mknod ()). .P If -.I pathname +.I path is absolute, then .I dirfd is ignored. @@ -158,14 +158,14 @@ is set to indicate the error. .B EACCES The parent directory does not allow write permission to the process, or one of the directories in the path prefix of -.I pathname +.I path did not allow search permission. (See also .BR path_resolution (7).) .TP .B EBADF .RB ( mknodat ()) -.I pathname +.I path is relative but .I dirfd is neither @@ -177,14 +177,15 @@ The user's quota of disk blocks or inodes on the filesystem has been exhausted. .TP .B EEXIST -.I pathname +.I path already exists. This includes the case where -.I pathname +.I path is a symbolic link, dangling or not. .TP .B EFAULT -.IR pathname " points outside your accessible address space." +.I path +points outside your accessible address space. .TP .B EINVAL .I mode @@ -193,14 +194,15 @@ special file, FIFO or socket. .TP .B ELOOP Too many symbolic links were encountered in resolving -.IR pathname . +.IR path . .TP .B ENAMETOOLONG -.IR pathname " was too long." +.I path +was too long. .TP .B ENOENT A directory component in -.I pathname +.I path does not exist or is a dangling symbolic link. .TP .B ENOMEM @@ -208,17 +210,17 @@ Insufficient kernel memory was available. .TP .B ENOSPC The device containing -.I pathname +.I path has no room for the new node. .TP .B ENOTDIR A component used as a directory in -.I pathname +.I path is not, in fact, a directory. .TP .B ENOTDIR .RB ( mknodat ()) -.I pathname +.I path is relative and .I dirfd is a file descriptor referring to a file other than a directory. @@ -234,11 +236,11 @@ capability); .\" Linux 2.2 and earlier; in Linux 2.4 and later, unprivileged can .\" use mknod() to make these files. also returned if the filesystem containing -.I pathname +.I path does not support the type of node requested. .TP .B EROFS -.I pathname +.I path refers to a file on a read-only filesystem. .SH VERSIONS POSIX.1-2001 says: "The only portable use of diff --git a/man/man2/mount_setattr.2 b/man/man2/mount_setattr.2 index bacc6e86b..3f315e990 100644 --- a/man/man2/mount_setattr.2 +++ b/man/man2/mount_setattr.2 @@ -15,7 +15,7 @@ Standard C library .BR "#include " " /* Definition of " SYS_* " constants */" .B #include .P -.BI "int syscall(SYS_mount_setattr, int " dirfd ", const char *" pathname , +.BI "int syscall(SYS_mount_setattr, int " dirfd ", const char *" path , .BI " unsigned int " flags ", struct mount_attr *" attr \ ", size_t " size ); .fi @@ -30,8 +30,8 @@ The .BR mount_setattr () system call changes the mount properties of a mount or an entire mount tree. If -.I pathname -is a relative pathname, +.I path +is relative, then it is interpreted relative to the directory referred to by the file descriptor .IR dirfd . @@ -40,11 +40,11 @@ If is the special value .BR AT_FDCWD , then -.I pathname +.I path is interpreted relative to the current working directory of the calling process. If -.I pathname +.I path is the empty string and .B AT_EMPTY_PATH is specified in @@ -104,7 +104,7 @@ The supported values are: .TP .B AT_EMPTY_PATH If -.I pathname +.I path is the empty string, change the mount properties on .I dirfd @@ -394,7 +394,7 @@ is set to indicate the error. .SH ERRORS .TP .B EBADF -.I pathname +.I path is relative but .I dirfd is neither @@ -421,7 +421,7 @@ but the mount still holds files open for writing. The pathname specified via the .I dirfd and -.I pathname +.I path arguments to .BR mount_setattr () isn't a mount point. @@ -924,10 +924,10 @@ with a structure which has every byte nonzero #include \& static inline int -mount_setattr(int dirfd, const char *pathname, unsigned int flags, +mount_setattr(int dirfd, const char *path, unsigned int flags, struct mount_attr *attr, size_t size) { - return syscall(SYS_mount_setattr, dirfd, pathname, flags, + return syscall(SYS_mount_setattr, dirfd, path, flags, attr, size); } \& @@ -938,11 +938,11 @@ open_tree(int dirfd, const char *filename, unsigned int flags) } \& static inline int -move_mount(int from_dirfd, const char *from_pathname, - int to_dirfd, const char *to_pathname, unsigned int flags) +move_mount(int from_dirfd, const char *from_path, + int to_dirfd, const char *to_path, unsigned int flags) { - return syscall(SYS_move_mount, from_dirfd, from_pathname, - to_dirfd, to_pathname, flags); + return syscall(SYS_move_mount, from_dirfd, from_path, + to_dirfd, to_path, flags); } \& static const struct option longopts[] = { diff --git a/man/man2/open.2 b/man/man2/open.2 index 49c641290..5966f8bcf 100644 --- a/man/man2/open.2 +++ b/man/man2/open.2 @@ -38,18 +38,18 @@ Standard C library .nf .B #include .P -.BI "int open(const char *" pathname ", int " flags ", ..." +.BI "int open(const char *" path ", int " flags ", ..." .BI " \f[R]/*\f[] mode_t " mode " \f[R]*/\f[] );" .P -.BI "int creat(const char *" pathname ", mode_t " mode ); +.BI "int creat(const char *" path ", mode_t " mode ); .P -.BI "int openat(int " dirfd ", const char *" pathname ", int " flags ", ..." +.BI "int openat(int " dirfd ", const char *" path ", int " flags ", ..." .BI " \f[R]/*\f[] mode_t " mode " \f[R]*/\f[] );" .P /* Documented separately, in \c .BR openat2 (2):\c \& */ -.BI "int openat2(int " dirfd ", const char *" pathname , +.BI "int openat2(int " dirfd ", const char *" path , .BI " const struct open_how *" how ", size_t " size ); .fi .P @@ -69,7 +69,7 @@ Feature Test Macro Requirements for glibc (see The .BR open () system call opens the file specified by -.IR pathname . +.IR path . If the specified file does not exist, it may optionally (if .B O_CREAT @@ -115,7 +115,7 @@ The open file description records the file offset and the file status flags (see below). A file descriptor is a reference to an open file description; this reference is unaffected if -.I pathname +.I path is subsequently removed or modified to refer to a different file. For further details on open file descriptions, see NOTES. .P @@ -248,7 +248,7 @@ flag to deal with this problem.) .TP .B O_CREAT If -.I pathname +.I path does not exist, create it as a regular file. .IP The owner (user ID) of the new file is set to the effective user ID @@ -392,7 +392,7 @@ is described in .TP .B O_DIRECTORY If -.I pathname +.I path is not a directory, cause the open to fail. .\" But see the following and its replies: .\" http://marc.theaimsgroup.com/?t=112748702800001&r=1&w=2 @@ -427,7 +427,7 @@ Ensure that this call creates the file: if this flag is specified in conjunction with .BR O_CREAT , and -.I pathname +.I path already exists, then .BR open () fails with the error @@ -436,7 +436,7 @@ fails with the error When these two flags are specified, symbolic links are not followed: .\" POSIX.1-2001 explicitly requires this behavior. if -.I pathname +.I path is a symbolic link, then .BR open () fails regardless of where the symbolic link points. @@ -450,7 +450,7 @@ There is one exception: on Linux 2.6 and later, can be used without .B O_CREAT if -.I pathname +.I path refers to a block device. If the block device is in use by the system (e.g., mounted), .BR open () @@ -530,7 +530,7 @@ One example is NFS, where the server maintains the access time. .TP .B O_NOCTTY If -.I pathname +.I path refers to a terminal device\[em]see .BR tty (4)\[em]it will not become the process's controlling terminal even if the @@ -538,7 +538,7 @@ process does not have one. .TP .B O_NOFOLLOW If the trailing component (i.e., basename) of -.I pathname +.I path is a symbolic link, then the open fails, with the error .BR ELOOP . Symbolic links in earlier components of the pathname will still be @@ -547,7 +547,7 @@ followed. .B ELOOP error that can occur in this case is indistinguishable from the case where an open fails because there are too many symbolic links found -while resolving components in the prefix part of the pathname.) +while resolving components in the path prefix of the pathname.) .IP This flag is a FreeBSD extension, which was added in Linux 2.1.126, and has subsequently been standardized in POSIX.1-2008. @@ -709,7 +709,7 @@ even when the subsequent operation (e.g., does not require read permission on the object. .IP If -.I pathname +.I path is a symbolic link and the .B O_NOFOLLOW flag is also specified, @@ -725,7 +725,7 @@ and with an empty pathname to have the calls operate on the symbolic link. .IP If -.I pathname +.I path refers to an automount point that has not yet been triggered, so no other filesystem is mounted on it, then the call returns a file descriptor referring to the automount directory without triggering a mount. @@ -786,7 +786,7 @@ See VERSIONS. .\" commit bb458c644a59dbba3a1fe59b27106c5e68e1c4bd Create an unnamed temporary regular file. The -.I pathname +.I path argument specifies a directory; an unnamed inode will be created in that directory's filesystem. Anything written to the resulting file will be lost when @@ -920,29 +920,29 @@ except for the differences described here. The .I dirfd argument is used in conjunction with the -.I pathname +.I path argument as follows: .IP \[bu] 3 If the pathname given in -.I pathname +.I path is absolute, then .I dirfd is ignored. .IP \[bu] If the pathname given in -.I pathname +.I path is relative and .I dirfd is the special value .BR AT_FDCWD , then -.I pathname +.I path is interpreted relative to the current working directory of the calling process (like .BR open ()). .IP \[bu] If the pathname given in -.I pathname +.I path is relative, then it is interpreted relative to the directory referred to by the file descriptor .I dirfd @@ -959,7 +959,7 @@ or using the flag. .P If the pathname given in -.I pathname +.I path is relative, and .I dirfd is not a valid file descriptor, an error @@ -968,7 +968,7 @@ results. (Specifying an invalid file descriptor number in .I dirfd can be used as a means to ensure that -.I pathname +.I path is absolute.) .\" .SS openat2(2) @@ -1000,7 +1000,7 @@ can fail with the following errors: .B EACCES The requested access to the file is not allowed, or search permission is denied for one of the directories in the path prefix of -.IR pathname , +.IR path , or the file did not exist yet and write access to the parent directory is not allowed. (See also @@ -1027,7 +1027,7 @@ in .TP .B EBADF .RB ( openat ()) -.I pathname +.I path is relative but .I dirfd is neither @@ -1039,7 +1039,7 @@ nor a valid file descriptor. was specified in .I flags and -.I pathname +.I path refers to a block device that is in use by the system (e.g., it is mounted). .TP .B EDQUOT @@ -1049,13 +1049,13 @@ is specified, the file does not exist, and the user's quota of disk blocks or inodes on the filesystem has been exhausted. .TP .B EEXIST -.I pathname +.I path already exists and .BR O_CREAT " and " O_EXCL were used. .TP .B EFAULT -.I pathname +.I path points outside your accessible address space. .TP .B EFBIG @@ -1097,18 +1097,18 @@ was specified. was specified in .I flags and the final component ("basename") of the new file's -.I pathname +.I path is invalid (e.g., it contains characters not permitted by the underlying filesystem). .TP .B EINVAL The final component ("basename") of -.I pathname +.I path is invalid (e.g., it contains characters not permitted by the underlying filesystem). .TP .B EISDIR -.I pathname +.I path refers to a directory and the access requested involved writing (that is, .B O_WRONLY @@ -1117,7 +1117,7 @@ or is set). .TP .B EISDIR -.I pathname +.I path refers to an existing directory, .B O_TMPFILE and one of @@ -1132,10 +1132,10 @@ functionality. .TP .B ELOOP Too many symbolic links were encountered in resolving -.IR pathname . +.IR path . .TP .B ELOOP -.I pathname +.I path was a symbolic link, and .I flags specified @@ -1151,14 +1151,14 @@ in .BR getrlimit (2)). .TP .B ENAMETOOLONG -.I pathname +.I path was too long. .TP .B ENFILE The system-wide limit on the total number of open files has been reached. .TP .B ENODEV -.I pathname +.I path refers to a device special file and no corresponding device exists. (This is a Linux kernel bug; in this situation .B ENXIO @@ -1170,11 +1170,11 @@ is not set and the named file does not exist. .TP .B ENOENT A directory component in -.I pathname +.I path does not exist or is a dangling symbolic link. .TP .B ENOENT -.I pathname +.I path refers to a nonexistent directory, .B O_TMPFILE and one of @@ -1198,23 +1198,23 @@ and the caller is not privileged; see Insufficient kernel memory was available. .TP .B ENOSPC -.I pathname +.I path was to be created but the device containing -.I pathname +.I path has no room for the new file. .TP .B ENOTDIR A component used as a directory in -.I pathname +.I path is not, in fact, a directory, or .B O_DIRECTORY was specified and -.I pathname +.I path was not a directory. .TP .B ENOTDIR .RB ( openat ()) -.I pathname +.I path is a relative pathname and .I dirfd is a file descriptor referring to a file other than a directory. @@ -1232,12 +1232,12 @@ The file is a UNIX domain socket. .TP .B EOPNOTSUPP The filesystem containing -.I pathname +.I path does not support .BR O_TMPFILE . .TP .B EOVERFLOW -.I pathname +.I path refers to a regular file that is too large to be opened. The usual scenario here is that an application compiled on a 32-bit platform without @@ -1268,23 +1268,23 @@ The operation was prevented by a file seal; see .BR fcntl (2). .TP .B EROFS -.I pathname +.I path refers to a file on a read-only filesystem and write access was requested. .TP .B ETXTBSY -.I pathname +.I path refers to an executable image which is currently being executed and write access was requested. .TP .B ETXTBSY -.I pathname +.I path refers to a file that is currently in use as a swap file, and the .B O_TRUNC flag was specified. .TP .B ETXTBSY -.I pathname +.I path refers to a file that is currently being read by the kernel (e.g., for module/firmware loading), and write access was requested. .TP @@ -1912,7 +1912,7 @@ and are specified in .I flags and the file specified by -.I pathname +.I path does not exist, .BR open () will create a regular file (i.e., diff --git a/man/man2/open_by_handle_at.2 b/man/man2/open_by_handle_at.2 index 6b9758d42..ab1e06903 100644 --- a/man/man2/open_by_handle_at.2 +++ b/man/man2/open_by_handle_at.2 @@ -14,7 +14,7 @@ Standard C library .BR "#define _GNU_SOURCE" " /* See feature_test_macros(7) */" .B #include .P -.BI "int name_to_handle_at(int " dirfd ", const char *" pathname , +.BI "int name_to_handle_at(int " dirfd ", const char *" path , .BI " struct file_handle *" handle , .BI " int *" mount_id ", int " flags ); .BI "int open_by_handle_at(int " mount_fd ", struct file_handle *" handle , @@ -43,7 +43,7 @@ system call returns a file handle and a mount ID corresponding to the file specified by the .I dirfd and -.I pathname +.I path arguments. The file handle is returned via the argument .IR handle , @@ -148,14 +148,14 @@ with the returned may fail. .P Together, the -.I pathname +.I path and .I dirfd arguments identify the file for which a handle is to be obtained. There are four distinct cases: .IP \[bu] 3 If -.I pathname +.I path is a nonempty string containing an absolute pathname, then a handle is returned for the file referred to by that pathname. In this case, @@ -163,22 +163,22 @@ In this case, is ignored. .IP \[bu] If -.I pathname +.I path is a nonempty string containing a relative pathname and .I dirfd has the special value .BR AT_FDCWD , then -.I pathname +.I path is interpreted relative to the current working directory of the caller, and a handle is returned for the file to which it refers. .IP \[bu] If -.I pathname +.I path is a nonempty string containing a relative pathname and .I dirfd is a file descriptor referring to a directory, then -.I pathname +.I path is interpreted relative to the directory referred to by .IR dirfd , and a handle is returned for the file to which it refers. @@ -187,7 +187,7 @@ and a handle is returned for the file to which it refers. for an explanation of why "directory file descriptors" are useful.) .IP \[bu] If -.I pathname +.I path is an empty string and .I flags specifies the value @@ -204,7 +204,7 @@ The .I mount_id argument returns an identifier for the filesystem mount that corresponds to -.IR pathname . +.IR path . This corresponds to the first field in one of the records in .IR /proc/self/mountinfo . Opening the pathname in the fifth field of that record yields a file @@ -219,13 +219,13 @@ in the error By default, .BR name_to_handle_at () does not dereference -.I pathname +.I path if it is a symbolic link, and thus returns a handle for the link itself. If .B AT_SYMLINK_FOLLOW is specified in .IR flags , -.I pathname +.I path is dereferenced if it is a symbolic link (so that the call returns a handle for the file referred to by the link). .P @@ -303,7 +303,7 @@ In addition, they can fail with the errors noted below. can fail with the following errors: .TP .B EFAULT -.IR pathname , +.IR path , .IR mount_id , or .I handle @@ -319,7 +319,7 @@ is greater than .BR MAX_HANDLE_SZ . .TP .B ENOENT -.I pathname +.I path is an empty string, but .B AT_EMPTY_PATH was not specified in @@ -334,7 +334,7 @@ and it is not the case that both includes .B AT_EMPTY_PATH and -.I pathname +.I path is an empty string. .TP .B EOPNOTSUPP @@ -358,7 +358,7 @@ can fail with the following errors: is not an open file descriptor. .TP .B EBADF -.I pathname +.I path is relative but .I dirfd is neither @@ -441,7 +441,7 @@ This sort of functionality allows a user-space file server to operate in a stateless fashion with respect to the files it serves. .P If -.I pathname +.I path refers to a symbolic link and .I flags does not specify @@ -574,15 +574,15 @@ int main(int argc, char *argv[]) { int mount_id, fhsize, flags, dirfd; - char *pathname; + char *path; struct file_handle *fhp; \& if (argc != 2) { - fprintf(stderr, "Usage: %s pathname\[rs]n", argv[0]); + fprintf(stderr, "Usage: %s path\[rs]n", argv[0]); exit(EXIT_FAILURE); } \& - pathname = argv[1]; + path = argv[1]; \& /* Allocate file_handle structure. */ \& @@ -597,8 +597,7 @@ main(int argc, char *argv[]) dirfd = AT_FDCWD; /* For name_to_handle_at() calls */ flags = 0; /* For name_to_handle_at() calls */ fhp\->handle_bytes = 0; - if (name_to_handle_at(dirfd, pathname, fhp, - &mount_id, flags) != \-1 + if (name_to_handle_at(dirfd, path, fhp, &mount_id, flags) != \-1 || errno != EOVERFLOW) { fprintf(stderr, "Unexpected result from name_to_handle_at()\[rs]n"); @@ -614,7 +613,7 @@ main(int argc, char *argv[]) \& /* Get file handle from pathname supplied on command line. */ \& - if (name_to_handle_at(dirfd, pathname, fhp, &mount_id, flags) == \-1) + if (name_to_handle_at(dirfd, path, fhp, &mount_id, flags) == \-1) err(EXIT_FAILURE, "name_to_handle_at"); \& /* Write mount ID, file handle size, and file handle to stdout, diff --git a/man/man2/openat2.2 b/man/man2/openat2.2 index 4ef28e9a6..5592015d0 100644 --- a/man/man2/openat2.2 +++ b/man/man2/openat2.2 @@ -15,7 +15,7 @@ Standard C library .BR "#include " " /* Definition of " SYS_* " constants */" .B #include .P -.BI "long syscall(SYS_openat2, int " dirfd ", const char *" pathname , +.BI "long syscall(SYS_openat2, int " dirfd ", const char *" path , .BI " struct open_how *" how ", size_t " size ); .fi .P @@ -34,7 +34,7 @@ and provides a superset of its functionality. The .BR openat2 () system call opens the file specified by -.IR pathname . +.IR path . If the specified file does not exist, it may optionally (if .B O_CREAT is specified in @@ -44,8 +44,8 @@ be created. As with .BR openat (2), if -.I pathname -is a relative pathname, then it is interpreted relative to the +.I path +is relative, then it is interpreted relative to the directory referred to by the file descriptor .I dirfd (or the current working directory of the calling process, if @@ -53,15 +53,15 @@ directory referred to by the file descriptor is the special value .BR AT_FDCWD ). If -.I pathname -is an absolute pathname, then +.I path +is absolute, then .I dirfd is ignored (unless .I how.resolve contains .BR RESOLVE_IN_ROOT , in which case -.I pathname +.I path is resolved relative to .IR dirfd ). .P @@ -80,7 +80,7 @@ argument must be specified as The .I how argument specifies how -.I pathname +.I path should be opened, and acts as a superset of the .I flags and @@ -166,7 +166,7 @@ or This is a bit-mask of flags that modify the way in which .B all components of -.I pathname +.I path will be resolved. (See .BR path_resolution (7) @@ -185,7 +185,7 @@ Do not permit the path resolution to succeed if any component of the resolution is not a descendant of the directory indicated by .IR dirfd . This causes absolute symbolic links (and absolute values of -.IR pathname ) +.IR path ) to be rejected. .IP Currently, this flag also disables magic-link resolution (see below). @@ -199,11 +199,11 @@ the caller should explicitly specify Treat the directory referred to by .I dirfd as the root directory while resolving -.IR pathname . +.IR path . Absolute symbolic links are interpreted relative to .IR dirfd . If a prefix component of -.I pathname +.I path equates to .IR dirfd , then an immediately following @@ -215,8 +215,8 @@ component likewise equates to is traditionally equivalent to .IR / ). If -.I pathname -is an absolute path, it is also interpreted relative to +.I path +is absolute, it is also interpreted relative to .IR dirfd . .IP The effect of this flag is as though the calling process had used @@ -280,7 +280,7 @@ an application may prefer to disable magic link resolution using the flag. .IP If the trailing component (i.e., basename) of -.I pathname +.I path is a magic link, .I how.resolve contains @@ -302,7 +302,7 @@ This option implies .BR RESOLVE_NO_MAGICLINKS . .IP If the trailing component (i.e., basename) of -.I pathname +.I path is a symbolic link, .I how.resolve contains @@ -321,13 +321,13 @@ Note that the effect of the .B RESOLVE_NO_SYMLINKS flag, which affects the treatment of symbolic links in all of the components of -.IR pathname , +.IR path , differs from the effect of the .B O_NOFOLLOW file creation flag (in .IR how.flags ), which affects the handling of symbolic links only in the final component of -.IR pathname . +.IR path . .IP Applications that employ the .B RESOLVE_NO_SYMLINKS @@ -348,7 +348,7 @@ so that a pathname component (now) contains a symbolic link. Disallow traversal of mount points during path resolution (including all bind mounts). Consequently, -.I pathname +.I path must either be on the same mount as the directory referred to by .IR dirfd , or on the same mount as the current working directory if diff --git a/man/man2/readlink.2 b/man/man2/readlink.2 index 44671cf3c..057b83349 100644 --- a/man/man2/readlink.2 +++ b/man/man2/readlink.2 @@ -24,14 +24,14 @@ Standard C library .B #include .P .BI "ssize_t readlink(size_t " bufsiz ; -.BI " const char *restrict " pathname , +.BI " const char *restrict " path , .BI " char " buf "[restrict " bufsiz "], size_t " bufsiz ); .P .BR "#include " "/* Definition of " AT_* " constants */" .B #include .P .BI "ssize_t readlinkat(size_t " bufsiz ; -.BI " int " dirfd ", const char *restrict " pathname , +.BI " int " dirfd ", const char *restrict " path , .BI " char " buf "[restrict " bufsiz "], size_t " bufsiz ); .P .fi @@ -57,7 +57,7 @@ Feature Test Macro Requirements for glibc (see .SH DESCRIPTION .BR readlink () places the contents of the symbolic link -.I pathname +.I path in the buffer .IR buf , which has size @@ -75,8 +75,8 @@ system call operates in exactly the same way as .BR readlink (), except for the differences described here. .P -If the pathname given in -.I pathname +If +.I path is relative, then it is interpreted relative to the directory referred to by the file descriptor .I dirfd @@ -86,26 +86,26 @@ the calling process, as is done by for a relative pathname). .P If -.I pathname +.I path is relative and .I dirfd is the special value .BR AT_FDCWD , then -.I pathname +.I path is interpreted relative to the current working directory of the calling process (like .BR readlink ()). .P If -.I pathname +.I path is absolute, then .I dirfd is ignored. .P Since Linux 2.6.39, .\" commit 65cfc6722361570bfe255698d9cd4dccaf47570d -.I pathname +.I path can be an empty string, in which case the call operates on the symbolic link referred to by .I dirfd @@ -139,7 +139,7 @@ Search permission is denied for a component of the path prefix. .TP .B EBADF .RB ( readlinkat ()) -.I pathname +.I path is relative but .I dirfd is neither @@ -161,7 +161,7 @@ is not positive. .TP .B EINVAL The named file (i.e., the final filename component of -.IR pathname ) +.IR path ) is not a symbolic link. .TP .B EIO @@ -184,7 +184,7 @@ A component of the path prefix is not a directory. .TP .B ENOTDIR .RB ( readlinkat ()) -.I pathname +.I path is relative and .I dirfd is a file descriptor referring to a file other than a directory. @@ -215,8 +215,8 @@ On older kernels where is unavailable, the glibc wrapper function falls back to the use of .BR readlink (). When -.I pathname -is a relative pathname, +.I path +is relative, glibc constructs a pathname based on the symbolic link in .I /proc/self/fd that corresponds to the @@ -273,7 +273,7 @@ main(int argc, char *argv[]) struct stat sb; \& if (argc != 2) { - fprintf(stderr, "Usage: %s \[rs]n", argv[0]); + fprintf(stderr, "Usage: %s \[rs]n", argv[0]); exit(EXIT_FAILURE); } \& diff --git a/man/man2/rmdir.2 b/man/man2/rmdir.2 index b8c491866..bcc113e62 100644 --- a/man/man2/rmdir.2 +++ b/man/man2/rmdir.2 @@ -17,7 +17,7 @@ Standard C library .nf .B #include .P -.BI "int rmdir(const char *" pathname ); +.BI "int rmdir(const char *" path ); .fi .SH DESCRIPTION .BR rmdir () @@ -31,58 +31,62 @@ is set to indicate the error. .TP .B EACCES Write access to the directory containing -.I pathname +.I path was not allowed, or one of the directories in the path prefix of -.I pathname +.I path did not allow search permission. (See also .BR path_resolution (7).) .TP .B EBUSY -.I pathname +.I path is currently in use by the system or some process that prevents its removal. On Linux, this means -.I pathname +.I path is currently used as a mount point or is the root directory of the calling process. .TP .B EFAULT -.IR pathname " points outside your accessible address space." +.I path +points outside your accessible address space. .TP .B EINVAL -.I pathname +.I path has .I . as last component. .TP .B ELOOP Too many symbolic links were encountered in resolving -.IR pathname . +.IR path . .TP .B ENAMETOOLONG -.IR pathname " was too long." +.I path +was too long. .TP .B ENOENT A directory component in -.I pathname +.I path does not exist or is a dangling symbolic link. .TP .B ENOMEM Insufficient kernel memory was available. .TP .B ENOTDIR -.IR pathname , +.IR path , or a component used as a directory in -.IR pathname , +.IR path , is not, in fact, a directory. .TP .B ENOTEMPTY -.I pathname +.I path contains entries other than -.IR . " and " .. " ;" +.I . +and +.IR .. ; or, -.I pathname +.I path has .I .. as its final component. @@ -93,7 +97,7 @@ for this condition. .TP .B EPERM The directory containing -.I pathname +.I path has the sticky bit .RB ( S_ISVTX ) set and the process's effective user ID is neither the user ID @@ -104,11 +108,11 @@ capability). .TP .B EPERM The filesystem containing -.I pathname +.I path does not support the removal of directories. .TP .B EROFS -.I pathname +.I path refers to a directory on a read-only filesystem. .SH STANDARDS POSIX.1-2008. diff --git a/man/man2/spu_create.2 b/man/man2/spu_create.2 index 401712911..03bce6bcb 100644 --- a/man/man2/spu_create.2 +++ b/man/man2/spu_create.2 @@ -20,8 +20,7 @@ Standard C library .BR "#include " " /* Definition of " SYS_* " constants */" .B #include .P -.BI "int syscall(SYS_spu_create, const char *" pathname \ -", unsigned int " flags , +.BI "int syscall(SYS_spu_create, const char *" path ", unsigned int " flags , .BI " mode_t " mode ", int " neighbor_fd ); .fi .P @@ -37,16 +36,16 @@ system call is used on PowerPC machines that implement the Cell Broadband Engine Architecture in order to access Synergistic Processor Units (SPUs). It creates a new logical context for an SPU in -.I pathname +.I path and returns a file descriptor associated with it. -.I pathname +.I path must refer to a nonexistent directory in the mount point of the SPU filesystem .RB ( spufs ). If .BR spu_create () is successful, a directory is created at -.I pathname +.I path and it is populated with the files described in .BR spufs (7). .P @@ -63,7 +62,7 @@ or closed; other operations are not defined. A logical SPU context is destroyed (along with all files created within the context's -.I pathname +.I path directory) once the last reference to the context has gone; this usually occurs when the file descriptor returned by .BR spu_create () @@ -107,7 +106,7 @@ In the future, gang scheduling may be implemented causing the group to be switched in and out as a single unit.) .IP A new directory will be created at the location specified by the -.I pathname +.I path argument. This gang may be used to hold other SPU contexts, by providing a pathname that is within the gang directory to further calls to @@ -181,25 +180,25 @@ mount point. An SPU context already exists at the given pathname. .TP .B EFAULT -.I pathname +.I path is not a valid string pointer in the calling process's address space. .TP .B EINVAL -.I pathname +.I path is not a directory in the .BR spufs (7) mount point, or invalid flags have been provided. .TP .B ELOOP Too many symbolic links were found while resolving -.IR pathname . +.IR path . .TP .B EMFILE The per-process limit on the number of open file descriptors has been reached. .TP .B ENAMETOOLONG -.I pathname +.I path is too long. .TP .B ENFILE @@ -211,7 +210,7 @@ SPU isolation. .TP .B ENOENT Part of -.I pathname +.I path could not be resolved. .TP .B ENOMEM @@ -229,7 +228,7 @@ loaded. .TP .B ENOTDIR A part of -.I pathname +.I path is not a directory. .TP .B EPERM @@ -239,7 +238,7 @@ flag has been given, but the user does not have the .B CAP_SYS_NICE capability. .SH FILES -.I pathname +.I path must point to a location beneath the mount point of .BR spufs . By convention, it gets mounted in diff --git a/man/man2/stat.2 b/man/man2/stat.2 index cfbfb654b..47ff9d22b 100644 --- a/man/man2/stat.2 +++ b/man/man2/stat.2 @@ -26,16 +26,16 @@ Standard C library .nf .B #include .P -.BI "int stat(const char *restrict " pathname , +.BI "int stat(const char *restrict " path , .BI " struct stat *restrict " statbuf ); .BI "int fstat(int " fd ", struct stat *" statbuf ); -.BI "int lstat(const char *restrict " pathname , +.BI "int lstat(const char *restrict " path , .BI " struct stat *restrict " statbuf ); .P .BR "#include " "/* Definition of " AT_* " constants */" .B #include .P -.BI "int fstatat(int " dirfd ", const char *restrict " pathname , +.BI "int fstatat(int " dirfd ", const char *restrict " path , .BI " struct stat *restrict " statbuf ", int " flags ); .fi .P @@ -69,14 +69,14 @@ No permissions are required on the file itself, but\[em]in the case of and .BR lstat ()\[em]execute (search) permission is required on all of the directories in -.I pathname +.I path that lead to the file. .P .BR stat () and .BR fstatat () retrieve information about the file pointed to by -.IR pathname ; +.IR path ; the differences for .BR fstatat () are described below. @@ -85,7 +85,7 @@ are described below. is identical to .BR stat (), except that if -.I pathname +.I path is a symbolic link, then it returns information about the link itself, not the file that the link refers to. .P @@ -136,8 +136,8 @@ which can still provide exactly the behavior of each of and .BR fstat (). .P -If the pathname given in -.I pathname +If +.I path is relative, then it is interpreted relative to the directory referred to by the file descriptor .I dirfd @@ -149,13 +149,13 @@ and for a relative pathname). .P If -.I pathname +.I path is relative and .I dirfd is the special value .BR AT_FDCWD , then -.I pathname +.I path is interpreted relative to the current working directory of the calling process (like .BR stat () @@ -163,7 +163,7 @@ and .BR lstat ()). .P If -.I pathname +.I path is absolute, then .I dirfd is ignored. @@ -174,7 +174,7 @@ can either be 0, or include one or more of the following flags ORed: .BR AT_EMPTY_PATH " (since Linux 2.6.39)" .\" commit 65cfc6722361570bfe255698d9cd4dccaf47570d If -.I pathname +.I path is an empty string (or NULL, since Linux 6.11) operate on the file referred to by @@ -202,13 +202,13 @@ to obtain its definition. .TP .BR AT_NO_AUTOMOUNT " (since Linux 2.6.38)" Don't automount the terminal ("basename") component of -.I pathname. +.I path. Since Linux 3.1 this flag is ignored. Since Linux 4.11 this flag is implied. .TP .B AT_SYMLINK_NOFOLLOW If -.I pathname +.I path is a symbolic link, do not dereference it: instead return information about the link itself, like .BR lstat (). @@ -231,7 +231,7 @@ is set to indicate the error. .B EACCES Search permission is denied for one of the directories in the path prefix of -.IR pathname . +.IR path . (See also .BR path_resolution (7).) .TP @@ -241,7 +241,7 @@ is not a valid open file descriptor. .TP .B EBADF .RB ( fstatat ()) -.I pathname +.I path is relative but .I dirfd is neither @@ -260,16 +260,16 @@ Invalid flag specified in Too many symbolic links encountered while traversing the path. .TP .B ENAMETOOLONG -.I pathname +.I path is too long. .TP .B ENOENT A component of -.I pathname +.I path does not exist or is a dangling symbolic link. .TP .B ENOENT -.I pathname +.I path is an empty string and .B AT_EMPTY_PATH was not specified in @@ -280,18 +280,18 @@ Out of memory (i.e., kernel memory). .TP .B ENOTDIR A component of the path prefix of -.I pathname +.I path is not a directory. .TP .B ENOTDIR .RB ( fstatat ()) -.I pathname +.I path is relative and .I dirfd is a file descriptor referring to a file other than a directory. .TP .B EOVERFLOW -.I pathname +.I path or .I fd refers to a file whose size, inode number, @@ -476,7 +476,7 @@ main(int argc, char *argv[]) struct stat sb; \& if (argc != 2) { - fprintf(stderr, "Usage: %s \[rs]n", argv[0]); + fprintf(stderr, "Usage: %s \[rs]n", argv[0]); exit(EXIT_FAILURE); } \& diff --git a/man/man2/statx.2 b/man/man2/statx.2 index 0abac75c1..03a7b9ba8 100644 --- a/man/man2/statx.2 +++ b/man/man2/statx.2 @@ -20,7 +20,7 @@ Standard C library .BR "#include " "/* Definition of " AT_* " constants */" .B #include .P -.BI "int statx(int " dirfd ", const char *_Nullable restrict " pathname , +.BI "int statx(int " dirfd ", const char *_Nullable restrict " path , .BI " int " flags ", unsigned int " mask , .BI " struct statx *restrict " statxbuf ); .fi @@ -101,12 +101,12 @@ but in the case of .BR statx () with a pathname, execute (search) permission is required on all of the directories in -.I pathname +.I path that lead to the file. .P .BR statx () uses -.IR pathname , +.IR path , .IR dirfd , and .I flags @@ -114,7 +114,7 @@ to identify the target file in one of the following ways: .TP An absolute pathname If -.I pathname +.I path begins with a slash, then it is an absolute pathname that identifies the target file. In this case, @@ -123,23 +123,23 @@ is ignored. .TP A relative pathname If -.I pathname +.I path is a string that begins with a character other than a slash and .I dirfd is .BR AT_FDCWD , then -.I pathname +.I path is a relative pathname that is interpreted relative to the process's current working directory. .TP A directory-relative pathname If -.I pathname +.I path is a string that begins with a character other than a slash and .I dirfd is a file descriptor that refers to a directory, then -.I pathname +.I path is a relative pathname that is interpreted relative to the directory referred to by .IR dirfd . @@ -149,7 +149,7 @@ for an explanation of why this is useful.) .TP By file descriptor If -.I pathname +.I path is an empty string (or NULL since Linux 6.11) and the .B AT_EMPTY_PATH flag is specified in @@ -167,7 +167,7 @@ is constructed by ORing together zero or more of the following constants: .B AT_EMPTY_PATH .\" commit 65cfc6722361570bfe255698d9cd4dccaf47570d If -.I pathname +.I path is an empty string (or NULL since Linux 6.11), operate on the file referred to by .I dirfd @@ -187,7 +187,7 @@ the call operates on the current working directory. .TP .B AT_NO_AUTOMOUNT Don't automount the terminal ("basename") component of -.I pathname +.I path if it is a directory that is an automount point. This allows the caller to gather attributes of an automount point (rather than the location it would mount). @@ -209,7 +209,7 @@ was set. .TP .B AT_SYMLINK_NOFOLLOW If -.I pathname +.I path is a symbolic link, do not dereference it: instead return information about the link itself, like .BR lstat (2). @@ -625,12 +625,12 @@ is set to indicate the error. .B EACCES Search permission is denied for one of the directories in the path prefix of -.IR pathname . +.IR path . (See also .BR path_resolution (7).) .TP .B EBADF -.I pathname +.I path is relative but .I dirfd is neither @@ -638,7 +638,7 @@ is neither nor a valid file descriptor. .TP .B EFAULT -.I pathname +.I path or .I statxbuf points to a location outside the process's accessible address space @@ -647,7 +647,8 @@ or is NULL .B AT_EMPTY_PATH is specified in .IR flags , -pathname is allowed to be NULL). +.I path +is allowed to be NULL). .TP .B EINVAL Invalid flag specified in @@ -664,14 +665,14 @@ with the value 0x80000000U.) Too many symbolic links encountered while traversing the pathname. .TP .B ENAMETOOLONG -.I pathname +.I path is too long. .TP .B ENOENT A component of -.I pathname +.I path does not exist, or -.I pathname +.I path is an empty string and .B AT_EMPTY_PATH was not specified in @@ -682,9 +683,9 @@ Out of memory (i.e., kernel memory). .TP .B ENOTDIR A component of the path prefix of -.I pathname +.I path is not a directory or -.I pathname +.I path is relative and .I dirfd is a file descriptor referring to a file other than a directory. diff --git a/man/man2/unlink.2 b/man/man2/unlink.2 index 47972bbc0..8a1492f89 100644 --- a/man/man2/unlink.2 +++ b/man/man2/unlink.2 @@ -20,12 +20,12 @@ Standard C library .nf .B #include .P -.BI "int unlink(const char *" pathname ); +.BI "int unlink(const char *" path ); .P .BR "#include " "/* Definition of " AT_* " constants */" .B #include .P -.BI "int unlinkat(int " dirfd ", const char *" pathname ", int " flags ); +.BI "int unlinkat(int " dirfd ", const char *" path ", int " flags ); .fi .P .RS -4 @@ -70,8 +70,8 @@ includes the flag) except for the differences described here. .P -If the pathname given in -.I pathname +If +.I path is relative, then it is interpreted relative to the directory referred to by the file descriptor .I dirfd @@ -82,22 +82,22 @@ and .BR rmdir (2) for a relative pathname). .P -If the pathname given in -.I pathname +If +.I path is relative and .I dirfd is the special value .BR AT_FDCWD , then -.I pathname +.I path is interpreted relative to the current working directory of the calling process (like .BR unlink () and .BR rmdir (2)). .P -If the pathname given in -.I pathname +If +.I path is absolute, then .I dirfd is ignored. @@ -114,14 +114,14 @@ By default, performs the equivalent of .BR unlink () on -.IR pathname . +.IR path . If the .B AT_REMOVEDIR flag is specified, it performs the equivalent of .BR rmdir (2) on -.IR pathname . +.IR path . .P See .BR openat (2) @@ -136,17 +136,16 @@ is set to indicate the error. .TP .B EACCES Write access to the directory containing -.I pathname +.I path is not allowed for the process's effective UID, or one of the directories in -.I pathname +.I path did not allow search permission. (See also .BR path_resolution (7).) .TP .B EBUSY -The file -.I pathname +.I path cannot be unlinked because it is being used by the system or another process; for example, it is a mount point @@ -154,29 +153,30 @@ or the NFS client software created it to represent an active but otherwise nameless inode ("NFS silly renamed"). .TP .B EFAULT -.I pathname +.I path points outside your accessible address space. .TP .B EIO An I/O error occurred. .TP .B EISDIR -.I pathname +.I path refers to a directory. (This is the non-POSIX value returned since Linux 2.1.132.) .TP .B ELOOP Too many symbolic links were encountered in translating -.IR pathname . +.IR path . .TP .B ENAMETOOLONG -.IR pathname " was too long." +.I path +was too long. .TP .B ENOENT A component in -.I pathname +.I path does not exist or is a dangling symbolic link, or -.I pathname +.I path is empty. .TP .B ENOMEM @@ -184,7 +184,7 @@ Insufficient kernel memory was available. .TP .B ENOTDIR A component used as a directory in -.I pathname +.I path is not, in fact, a directory. .TP .B EPERM @@ -201,7 +201,7 @@ The filesystem does not allow unlinking of files. .TP .BR EPERM " or " EACCES The directory containing -.I pathname +.I path has the sticky bit .RB ( S_ISVTX ) set and the process's effective UID is neither the UID of the file to @@ -216,7 +216,7 @@ The file to be unlinked is marked immutable or append-only. .BR FS_IOC_SETFLAGS (2const).) .TP .B EROFS -.I pathname +.I path refers to a file on a read-only filesystem. .P The same errors that occur for @@ -229,7 +229,7 @@ The following additional errors can occur for .BR unlinkat (): .TP .B EBADF -.I pathname +.I path is relative but .I dirfd is neither @@ -241,14 +241,14 @@ An invalid flag value was specified in .IR flags . .TP .B EISDIR -.I pathname +.I path refers to a directory, and .B AT_REMOVEDIR was not specified in .IR flags . .TP .B ENOTDIR -.I pathname +.I path is relative and .I dirfd is a file descriptor referring to a file other than a directory. @@ -273,8 +273,8 @@ is unavailable, the glibc wrapper function falls back to the use of or .BR rmdir (2). When -.I pathname -is a relative pathname, +.I path +is relative, glibc constructs a pathname based on the symbolic link in .I /proc/self/fd that corresponds to the diff --git a/man/man2/utimensat.2 b/man/man2/utimensat.2 index 45bdd47dd..dafc71d62 100644 --- a/man/man2/utimensat.2 +++ b/man/man2/utimensat.2 @@ -15,7 +15,7 @@ Standard C library .BR "#include " " /* Definition of " AT_* " constants */" .B #include .P -.BI "int utimensat(int " dirfd ", const char *" pathname , +.BI "int utimensat(int " dirfd ", const char *" path , .BI " const struct timespec " times "[_Nullable 2], int " flags ); .BI "int futimens(int " fd ", const struct timespec " times "[_Nullable 2]);" .fi @@ -55,7 +55,7 @@ when setting file timestamps. With .BR utimensat () the file is specified via the pathname given in -.IR pathname . +.IR path . With .BR futimens () the file whose timestamps are to be updated is specified via @@ -152,7 +152,7 @@ but other error conditions may still be detected. .\" .SS utimensat() specifics If -.I pathname +.I path is relative, then by default it is interpreted relative to the directory referred to by the open file descriptor, .I dirfd @@ -165,19 +165,19 @@ See for an explanation of why this can be useful. .P If -.I pathname +.I path is relative and .I dirfd is the special value .BR AT_FDCWD , then -.I pathname +.I path is interpreted relative to the current working directory of the calling process (like .BR utimes (2)). .P If -.I pathname +.I path is absolute, then .I dirfd is ignored. @@ -190,7 +190,7 @@ the following values defined in .TP .BR AT_EMPTY_PATH " (since Linux 5.8)" If -.I pathname +.I path is an empty string, operate on the file referred to by .I dirfd (which may have been obtained using the @@ -211,7 +211,7 @@ to obtain its definition. .TP .B AT_SYMLINK_NOFOLLOW If -.I pathname +.I path specifies a symbolic link, then update the timestamps of the link, rather than the file to which it refers. .SH RETURN VALUE @@ -271,7 +271,7 @@ is not a valid file descriptor. .TP .B EBADF .RB ( utimensat ()) -.I pathname +.I path is relative but .I dirfd is neither @@ -285,7 +285,7 @@ pointed to an invalid address; or, was .BR AT_FDCWD , and -.I pathname +.I path is NULL or an invalid address. .TP .B EINVAL @@ -305,7 +305,7 @@ fields. .TP .B EINVAL .\" SUSv4 does not specify this error. -.I pathname +.I path is NULL, .I dirfd is not @@ -318,32 +318,32 @@ contains .B ELOOP .RB ( utimensat ()) Too many symbolic links were encountered in resolving -.IR pathname . +.IR path . .TP .B ENAMETOOLONG .RB ( utimensat ()) -.I pathname +.I path is too long. .TP .B ENOENT .RB ( utimensat ()) A component of -.I pathname +.I path does not refer to an existing directory or file, or -.I pathname +.I path is an empty string. .TP .B ENOTDIR .RB ( utimensat ()) -.I pathname -is a relative pathname, but +.I path +is relative, but .I dirfd is neither .B AT_FDCWD nor a file descriptor referring to a directory; or, one of the prefix components of -.I pathname +.I path is not a directory. .TP .B EPERM @@ -390,7 +390,7 @@ The file is on a read-only filesystem. .B ESRCH .RB ( utimensat ()) Search permission is denied for one of the prefix components of -.IR pathname . +.IR path . .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). @@ -416,7 +416,7 @@ system call. To support this, the Linux .BR utimensat () system call implements a nonstandard feature: if -.I pathname +.I path is NULL, then the call modifies the timestamps of the file referred to by the file descriptor .I dirfd @@ -434,7 +434,7 @@ utimensat(fd, NULL, times, 0); Note, however, that the glibc wrapper for .BR utimensat () disallows passing NULL as the value for -.IR pathname : +.IR path : the wrapper function returns the error .B EINVAL in this case. @@ -473,7 +473,7 @@ then the Linux implementation of succeeds even if the file referred to by .I dirfd and -.I pathname +.I path does not exist. .SH BUGS Several bugs afflict