diff options
Diffstat (limited to 'man2/unlink.2')
-rw-r--r-- | man2/unlink.2 | 44 |
1 files changed, 22 insertions, 22 deletions
diff --git a/man2/unlink.2 b/man2/unlink.2 index c43071f12..446415bd3 100644 --- a/man2/unlink.2 +++ b/man2/unlink.2 @@ -30,7 +30,7 @@ Standard C library .P .RS -4 Feature Test Macro Requirements for glibc (see -.BR feature_test_macros (7)): +.MR feature_test_macros 7 ): .RE .P .BR unlinkat (): @@ -62,7 +62,7 @@ The system call operates in exactly the same way as either .BR unlink () or -.BR rmdir (2) +.MR rmdir 2 (depending on whether or not .I flags includes the @@ -79,7 +79,7 @@ referred to by the file descriptor the calling process, as is done by .BR unlink () and -.BR rmdir (2) +.MR rmdir 2 for a relative pathname). .P If the pathname given in @@ -94,7 +94,7 @@ is interpreted relative to the current working directory of the calling process (like .BR unlink () and -.BR rmdir (2)). +.MR rmdir 2 ). .P If the pathname given in .I pathname @@ -119,12 +119,12 @@ If the .B AT_REMOVEDIR flag is specified, then performs the equivalent of -.BR rmdir (2) +.MR rmdir 2 on .IR pathname . .P See -.BR openat (2) +.MR openat 2 for an explanation of the need for .BR unlinkat (). .SH RETURN VALUE @@ -142,7 +142,7 @@ directories in .I pathname did not allow search permission. (See also -.BR path_resolution (7).) +.MR path_resolution 7 .) .TP .B EBUSY The file @@ -213,7 +213,7 @@ capability). .B EPERM The file to be unlinked is marked immutable or append-only. (See -.BR ioctl_iflags (2).) +.MR ioctl_iflags 2 .) .TP .B EROFS .I pathname @@ -222,7 +222,7 @@ refers to a file on a read-only filesystem. The same errors that occur for .BR unlink () and -.BR rmdir (2) +.MR rmdir 2 can also occur for .BR unlinkat (). The following additional errors can occur for @@ -271,7 +271,7 @@ On older kernels where is unavailable, the glibc wrapper function falls back to the use of .BR unlink () or -.BR rmdir (2). +.MR rmdir 2 . When .I pathname is a relative pathname, @@ -284,15 +284,15 @@ argument. Infelicities in the protocol underlying NFS can cause the unexpected disappearance of files which are still being used. .SH SEE ALSO -.BR rm (1), -.BR unlink (1), -.BR chmod (2), -.BR link (2), -.BR mknod (2), -.BR open (2), -.BR rename (2), -.BR rmdir (2), -.BR mkfifo (3), -.BR remove (3), -.BR path_resolution (7), -.BR symlink (7) +.MR rm 1 , +.MR unlink 1 , +.MR chmod 2 , +.MR link 2 , +.MR mknod 2 , +.MR open 2 , +.MR rename 2 , +.MR rmdir 2 , +.MR mkfifo 3 , +.MR remove 3 , +.MR path_resolution 7 , +.MR symlink 7 |